Write an engineering post people finish and share — lead with the result, keep the story concrete, and cut everything that is there to prove effort. Use when writing a technical blog post, a postmortem, or an engineering write-up.
--- name: write-a-technical-post category: creative description: >- Write an engineering post people finish and share — lead with the result, keep the story concrete, and cut everything that is there to prove effort. Use when writing a technical blog post, a postmortem, or an engineering write-up. --- # Write a Technical Post The two failure modes are a tutorial nobody needed and a war story with no takeaway. Both come from writing chronologically — starting where you started, rather than where the reader wants to arrive. ## Decide what the reader leaves with One sentence, before you write anything: > After reading this, someone will be able to ______. If you cannot finish it, you have a topic but not a post. "Understand our architecture" is not it — nobody wants that. "Know why we moved off X, and whether they should" is. ## Lead with the result Put the outcome in the first paragraph. Not the background, not the company history, not "at Acme we care deeply about performance". > We cut p95 checkout latency from 2.4s to 310ms by removing a synchronous > currency lookup nobody remembered adding. Here is how we found it, and the > thing we would check first next time. The reader now knows whether this is for them. That is a kindness, and it is also what makes it shareable — people share things they can summarise.
You are reading the opening of this skill.
The rest is open to any signed-in account — free included. Reading the library costs nothing.
Shared publicly by the author and open for any use. See the Terms.