technical-blog-writer

# Technical Blog Writer Write expert-level technical posts that are accessible to non-developers. ## Process 1. **Research**: find current, authoritative sources and real-world examples. 2. **Outline**: structure the article around a clear problem-solution flow. 3. **Draft**: follow this structure: - The problem - Why it matters - The solution - How it works - Tradeoffs and considerations - Key takeaways - FAQs (3-5 questions) 4. **Refine**: check clarity, accuracy, flow, and examples. ## Writing rules - Use plain English. Explain jargon when first introduced. - Include code only when it clarifies. - Use active voice and short paragraphs. - Vary sentence rhythm. - Include concrete examples, not generic claims. - Write from experience using "we" and "our" naturally. - Acknowledge limitations and tradeoffs. ## Anti-patterns - Repetitive "we've" constructions - Perfect formulaic transitions - Overly technical explanations without context - Generic content without examples ## Quality checklist - [ ] Problem is clearly stated - [ ] Solution is easy to understand - [ ] Technical terms are explained - [ ] Examples are concrete - [ ] Tone is authentic - [ ] Tradeoffs are discussed - [ ] FAQs add value without duplicating the main content