Why a writing habit pays off

I started writing in public because a colleague told me I explained things better out loud than in a design document, and that this was not a compliment. Four years later the habit has changed how I work more than any tool I picked up in the same period. This is what it actually does, and what it does not.

What the habit is

Not a blog strategy. A habit: a fixed slot, a small target, and a rule that something gets published even when it is unremarkable. Mine is forty minutes on weekday mornings and one post a fortnight, which over a year produces roughly twenty-five pieces, of which maybe six are any good. The other nineteen are the price of the six.

The payoff is not the audience. It is that writing forces a claim into a sentence, and a sentence can be wrong in a way a vague feeling cannot. Half the posts I abandon get abandoned because writing them revealed I did not understand the thing yet. That is the habit working, not failing.

Why it stays fun

Because the format is forgiving. A post can be four hundred words about one flag you got wrong, and that will help somebody more than a two-thousand-word survey of a field you barely know. Some of the pieces that get the most replies are the ones I wrote in an hour after an incident, while I was still annoyed.

It also does not have to be earnest. A short, funny write-up of a bug is real technical writing — the reader still learns the failure mode, they just enjoy the trip. The posts I reread years later are almost never the serious ones.

Tips that actually helped

Write from the end: decide the one sentence you want a reader to keep, and cut anything that does not serve it. Keep a running file of half-ideas so you never face a blank page on habit day. Publish before you are comfortable; the extra polish buys less than the extra reader. And answer every thoughtful reply, at least for the first year — the conversations are where the next three posts come from.

The tip I resisted longest was the useful one: pick a narrow lane. “Notes from maintaining a build system” gets read. “Thoughts on software” does not.

Conclusion

A writing habit is a thinking tool that happens to leave a public artefact. It made me faster at design documents, better in incident reviews, and much harder to bluff in an interview, because I had already argued most of my positions with myself in writing.

If you take one thing from this: make the target small enough that you cannot reasonably skip it, and let the quality average out over a year rather than agonising over any single post. Writing should be something you look forward to on a Tuesday morning, not a debt you owe an audience.