📌 Quick Info
- Topic: Why writing is a developer skill
- Target Audience: Developers who think writing isn't their job
- Goal: Show that writing = thinking, and thinking = better code
1. Introduction
"I used to think writing was something 'other people' did. Then I started writing about code, and my code got better. Here's why."
2. The Assumption I Used to Have
For a long time, I thought writing and coding were two separate skills.
Coders write code. Writers write words. Different people. Different jobs.
I was wrong. And it took publishing 9 articles to see it.
3. What Writing Actually Does to Your Code
Writing forces clarity.
When you have to explain range(1, 6) to a beginner, you can't hand-wave. You have to actually know what it does, why it stops at 5, and where people get confused. Writing exposes the parts of your understanding that are still fuzzy.
Writing catches bugs before they ship.
Half the bugs I've found in my own code came from writing about it. When you explain line by line, you notice the missing edge case. You notice the variable name that doesn't match what it's doing.
Writing is thinking made visible.
If you can't explain it clearly, you don't understand it yet. Writing is the test.
4. The Developer Who Can't Write
Here's what happens when developers don't write:
- Their PR descriptions are one line: "fix bug"
- Their commit messages are "update"
- Their documentation is out of date or missing
- Their code reviews are vague: "this feels wrong"
- Their interviews go badly because they can't explain their own work
None of those are coding problems. All of them are writing problems.
5. The Developer Who Can Write
Here's what happens when they do:
- Their PRs get merged faster because reviewers understand the intent
- Their commits tell a story
- Their docs actually help the next person
- Their code reviews lift the whole team
- Their interviews go well because they can talk about their work
- They get asked to write blog posts, give talks, and lead projects
Writing is a force multiplier on top of coding. It doesn't replace the skill — it amplifies it.
6. The AI Era Makes This More True
AI can write code now. It can't explain why the code matters.
The people who win in the AI era won't be the ones who type the most code. They'll be the ones who:
- Understand what the code is supposed to do
- Can explain it to non-engineers
- Can write about decisions and trade-offs
- Can document systems that other people need to maintain
All of those are writing skills.
7. What I'd Tell a Developer Who Hates Writing
You don't have to write blog posts. You don't have to publish articles.
But you should write:
- Clear commit messages — future you will thank present you
- Real PR descriptions — explain why, not just what
- Documentation that isn't just autogenerated — add the "why"
- Comments that explain decisions, not syntax
Start there. And if you find you enjoy it, write something public. Even one article changes how you see your own work.
8. Conclusion
"Writing didn't make me a worse developer. It made me a better one — because it forced me to actually understand what I was doing. Every developer should write. Not to become a writer. To become a better developer."
Top comments (0)