How Writing Made Me a Better Developer

What Does Writing Have to Do With Coding?

When I first heard these two were connected, I thought "what are you talking about?" For developers, algorithms matter — not prose. But after two years of blogging, my mind changed. Writing builds the ability to structure your thinking. And that's remarkably similar to structuring code.

Code Is Writing for an Audience

Choosing good variable names, splitting functions appropriately, writing clear comments — all of these are acts done for the reader. It's the same as considering your audience when writing. I need to write code that not me, but future-me in 6 months can understand. Code that other team members can understand.

After spending so much time asking "is this sentence clear to the reader?" while blogging, I naturally started asking "is this function name clear to other developers?" while coding.

My PR Descriptions Transformed

My PR descriptions before writing: "Fixed login feature." That's it.

My PR descriptions after writing: "Fixed bug where session expiration didn't trigger auto-logout. Root cause: token refresh logic was comparing expiration time in local time instead of UTC. Change: unified all time comparisons to UTC."

This difference completely changed code review speed. Reviewers grasped context immediately, so feedback came faster. It contributed to the entire team's development velocity.

(Though I didn't write like this from the start. I'm pretty sure my team lead told me "write more detailed PR descriptions" at least 3 times.)

The Power of Internal Documentation

Onboarding docs, architecture decision records (ADRs), incident reports. Writing these built a habit of articulating technical judgments in prose. When you write "why did I choose this technology?" you start seeing holes in your own reasoning.

Once, while writing a proposal to adopt a new library, I thought "my evidence is weak." I ran benchmarks and discovered it was actually slower than the existing library. If I'd proposed it verbally instead of in writing, it might have gotten approved. Writing prevented a bad decision.

Mistake: I Write Too Long

My weakness is that my writing gets long. When Slack messages go over 5 lines, readership drops. Technical docs should lead with the key point and put details after, but I have a habit of starting with lengthy background explanations.

I'm trying to fix this with the "BLUF (Bottom Line Up Front)" principle. Write the conclusion first, then the reasoning. It hasn't fully become second nature yet, but being conscious of it is helping.

Has Blogging Helped My Career?

Honestly, the direct impact was less than expected. I didn't land a job because of my blog or become famous. Average views per post: about 127.

But the indirect effects are significant. Writing deepened my technical understanding, and better articulation made me more persuasive in meetings. These aren't changes you can measure in numbers, but they're definitely noticeable.

If you ask whether writing directly impacts development skills — I think it does. But that's my experience, and there are plenty of great developers who don't write. I just know that starting to write has zero downside.