The useful version of “in public”
There is a version of building in public that turns every half-formed thought into content. I am more interested in the quieter version: leaving a trail that helps me see how an idea changed, why a decision made sense at the time, and what I would try differently now.
The audience can be real without becoming the reason for every choice.
Document decisions, not just milestones
A list of finished features rarely explains the work. The interesting material is usually one layer beneath it:
- What did I think the problem was?
- What evidence changed that view?
- Which constraint became useful?
- What did the prototype make newly visible?
- What am I deliberately leaving unresolved?
These questions produce notes that are useful even when the project never becomes a polished launch.
Leave room for uncertainty
Writing “I don’t know yet” is not a failure of documentation. It preserves the actual state of the work. When I return later, I can distinguish an open question from an answer I have simply forgotten.
A good project log is less like a press release and more like a conversation with your future self.
The habit I want
I want publishing to be lightweight enough that reflection happens while the details are still alive. That is why this site keeps writing in plain Markdown files: a title, a few lines of context, and the note itself. No dashboard to maintain and no database standing between the thought and the page.