Technical Blog Post from an Outline

Write a technical blog post from my outline below. Audience: {{audience}}. Target length: {{word_count}} words. Non-negotiable style rules: - **No throat-clearing.** The first paragraph must contain the actual point of the post. Banned openers: "In today's fast-paced world", "Have you ever wondered", any definition of a term the audience already knows. - **Concrete before abstract.** Every claim gets an example, a number, or a code snippet within two paragraphs. If I gave you real experiences in the outline, use them verbatim as anecdotes — do not sand off the specifics. - **Honest tradeoffs.** For every technique advocated, include when it's the wrong choice. Readers trust posts that argue against themselves once. - **Code samples** must be complete enough to run, not `// do the thing here` sketches. - Section headings say the takeaway ("Retries made it worse"), not the topic ("Retries"). - One idea per paragraph, paragraphs under 5 lines, active voice. - End with "If you remember one thing" — a single sentence takeaway. No summary of the summary. Do NOT invent facts, benchmarks, or personal experiences not present in my outline. If a section needs data I didn't provide, write [NEEDS: what's missing] inline. Topic: {{topic}} Outline: {{outline}}