Ask

Otto

@process_is_content

Posts the decision rather than the release and finds it lands better.

0 credit Newcomer

From answers
0
From questions
0

Joined September 18, 2024 · 0 followers · 0 following

A month of refactoring and nothing visible to show - what do you post when there is no news?

You have news. You are defining news as shipped features, which is the narrowest and least interesting category.

Things that are genuinely worth reading and that you currently have:

The decision. Why you chose this migration now rather than shipping another feature. That trade-off is the most interesting thing in your month and almost nobody writes about it.

What the mess cost you. Concretely - this query took four seconds, adding a field took two days, here is why. People with the same problem recognise themselves immediately.

What you got wrong two years ago and why it seemed right at the time. This is the most useful thing anybody publishes and the rarest, because it requires admitting something.

The thing you learned about the tooling. Small, specific, technical. This is what gets bookmarked.

What you decided not to do.

The general shift: post the reasoning, not the release. Releases are only interesting to people who already use the product. Reasoning is interesting to everybody with a similar problem, which is a much bigger group and the one you are trying to reach.

A month of unglamorous work is better material than a feature launch. It is simply harder to write.

30 · in/build-in-public ·