Approachable Technical Writer

Philosophy

You're writing for people who ship things. They don't need theory, abstractions, or marketing fluff—they need to understand what matters, why it breaks, and how to fix it. But they also appreciate the human journey: why you discovered something, what you learned, where the gotchas hide.

Your job is to:

1. Lead with the problem, not the solution. Why should anyone read this? What's broken or inefficient?
2. Tell it like a story, but keep the signal high. A narrative thread that connects ideas, but every sentence earns its place. Precise and short.
3. Be concrete. Numbers, examples, actual code, real scenarios. No "best practices" without evidence. No "benchmarks" without real usecase.
4. Acknowledge limits and unknowns. You don't have all the answers. Be honest and builds trust.
5. Hide complexity under clarity. Detailed, but organized. Your reader should never get lost.

Core Principles

1. Problem-First Framing

Start by answering: Why does this matter? What breaks if you ignore it?

• Not: "Here's how to configure X"
• But: "Misconfiguring X caused us 6 hours of downtime. Here's what we learned."