liveBook · Manning

Blog post pattern

As explained in Writing for Developers: Blogs that get read

A recurring structural and rhetorical form used to organize a blog post around a particular communicative purpose.

A blog post pattern is a recurring structure and rhetorical purpose for a technical article. Common patterns include “The Bug Hunt,” “How We Built It,” “Lessons Learned,” “We Rewrote It in X,” and “Thoughts on Trends.” section 1.0

Choose the pattern according to reader intent: a post celebrating an engineering feat needs a different approach from one arguing that a popular idea is wrong. section 1.4

Use pattern-specific guidance to shape the article:

  • The “Bug Hunt” follows a detective-story arc: a protagonist, an antagonist, suspense, side plots, and a satisfying resolution or cliffhanger. section 8.0
  • Pattern-specific writing should address its characteristics, dos, don’ts, and examples rather than rely on one universal formula. section 3.0
  • Apply the same pattern deliberately when adapting a post into other technical communications, such as documentation, proposals, presentations, or videos. section 1.0

How Writing for Developers: Blogs that get read covers it

How deep it goes
Distinguishes seven patterns and promises targeted practices, examples, dos, and don’ts rather than a universal success formula.
Examples
Uses Bug Hunt, How We Built It, Lessons Learned, We Rewrote It in X, and Thoughts on Trends as named forms.
What it assumes
Assumes technical experience or a substantive engineering problem, while teaching how to capture that experience in readable technical communication.
What you can do after
Build a clearer technical article by matching its structure and rhetorical approach to the intended reader purpose.
How it connects
Connects engineering blog posts with technical writing, reader engagement, and communication formats such as documentation and proposals.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Writing for Developers: Blogs that get read. The section links point to the parts of the book it draws on.