Nobody writes about the boring parts

The advice is always the same: publish consistently. Weekly, ideally. Show up, build an audience, compound.

The advice never mentions that the work does not arrive weekly.

Some weeks you ship something genuinely new and there is more to say than fits. Most weeks you are paying down debt - moving something to new hosting, fixing a thing that should have been right the first time, discovering that a change made months ago quietly broke something adjacent. Nothing to announce. Nothing that photographs well.

So the calendar and the work disagree, and the usual resolution is to write filler on the quiet weeks. Which is the worst available option, and I want to argue the opposite.

The quiet weeks are the better material

Everyone announces features. Almost nobody documents what broke.

Think about what you actually learn from in someone else's writing. Rarely the launch post. Usually the one where they explain that the DNS record they were about to bulk-edit also happened to be the one their email depended on, and how close that came to being a very bad afternoon. That post is worth more than any feature announcement, because it is the thing you cannot get from documentation and will otherwise only get by making the mistake yourself.

The reason nobody writes it is that it does not feel like progress. It feels like admitting the week was spent on maintenance. But maintenance is where the transferable knowledge lives - the launch was specific to that product, and the trap you fell into is specific to nothing at all.

Lumpy work, smooth calendar

Two things make the disagreement tractable, and neither requires pretending.

Bank what does not depend on the week. If you already know six things worth writing about, write all six while the context is hot and release them one at a time. Batching suits writing far better than a weekly scramble does - you were already thinking about it, and the marginal cost of the fourth piece is much lower than the first. That covers the weeks with nothing new to say.

And treat the maintenance weeks as a different genre, not a failed version of the good ones. They do not produce announcements. They produce the operational lesson, the near miss, the thing that turned out to be more subtle than expected. That is its own kind of post and it needs no news to justify it.

Do both and cadence stops depending on having had a good week - which is the actual problem, since you cannot schedule those.

A gap beats filler

One rule holds the whole thing together.

A missed week costs almost nothing. Nobody is sitting there waiting; they will read the next one whenever it arrives.

One interchangeable post costs a great deal, because it teaches people that opening your writing is not reliably worth the click. That lesson is expensive to un-teach, and it is learned from a single weak piece far faster than it is unlearned from three good ones.

So the honest version of "publish consistently" is: publish when there is something worth reading, arrange your work so that happens more often than chance would allow, and let the gaps be gaps.

Which mostly means noticing that the boring weeks were never actually boring. They were just the parts nobody writes down.

← All writing