Writing is the most underrated engineering skill. It sharpens thinking, creates leverage, and compounds over a career in ways that code alone cannot.
Most engineers treat writing as overhead: the README you write after the code is done, the doc you update reluctantly. This is a mistake.
Writing Clarifies Thinking
The act of writing forces you to be specific. Vague ideas that feel coherent in your head reveal their gaps when you try to express them in sentences.
If you can't explain what a system does in one paragraph, you probably don't understand it as well as you think you do. Writing is the test.
This is why the best engineers write. Not to communicate what they already know, but to discover what they actually think.
Writing Creates Leverage
A decision you explain once in a meeting influences one conversation. A decision you write down clearly can influence everyone who joins the team in the next three years.
Documentation, design documents, incident post-mortems, onboarding guides: these aren't overhead. They're leverage. They let your thinking scale beyond the conversations you're physically in.
Writing Compounds Over Time
Code becomes legacy. Architecture becomes archaeology. But a well-written explanation of why a decision was made compounds in value as the team grows and people forget.
Writing also compounds for the writer. Every piece you write is evidence of how you think. Over years, it becomes a track record, not of what you built, but of how you reason.
Start Before You're Ready
The biggest mistake is waiting until you have something worth saying. Write about problems you're working through. Write about what you learned this week. Write about what confused you and how you resolved it.
The first things you write will be rough. Write them anyway. Clarity comes from practice, not from waiting.
The compounding starts when you start.