What to write in a build-in-public update (when your day felt boring)
A practical answer to the question that stalls most daily logs: "I didn't do anything worth posting today — what do I even write?"
Most build-in-public habits don't die on the dramatic days. They die on the ordinary ones — the day you fixed a config, read some docs, and went to bed, and then stared at an empty box thinking nobody wants to read that. So you skip it. Then you skip the next one. The blank page, not the lack of progress, is what breaks the chain.
The fix is to stop treating the update as a highlight reel. A daily log is a record, not a performance. Its first job is to exist. Here's what to write when the day felt like nothing.
1. Answer one concrete question instead of "summarizing"
"Summarize your day" is a hard, open-ended task, which is why you freeze. Answering a specific question is easy. Pick one and just respond to it:
- What's one thing you moved forward, even a little?
- What did you learn or figure out today?
- What got you stuck — and how did you get unstuck?
- What did you decide not to do?
- What will make tomorrow easier?
- What did you ship, fix, or delete?
Any one of these turns a blank page into a fill-in-the-blank. You almost always have an answer to at least one, even after a slow day.
2. "Boring" maintenance work is the most relatable thing you can post
Refactoring, fixing a flaky test, renaming things, reading documentation, deleting dead code — this is what the actual job is most days, and almost nobody posts it because it doesn't feel impressive. That's exactly why it lands: other builders recognize their own week in it. "Spent an hour tracking down why a date was off by one" is more honest and more useful than another launch announcement.
3. Write it for one specific person, not "an audience"
If you imagine broadcasting to a crowd, every sentence has to justify itself and nothing is good enough. Instead, write the note you'd send a friend who's also building something — one line, no polish, "here's what I did today." That framing lowers the bar to where you can actually clear it, and it reads as more genuine than performed enthusiasm.
4. One honest sentence beats a paragraph you never post
There is no minimum length for a valid update. "Fixed the signup bug, tired, back at it tomorrow" is a complete, legitimate entry. The value of a daily log comes from the daily part — the unbroken record of showing up — not from any single entry being good. A short true line every day compounds; a great post once a month doesn't.
5. Log the flat days especially, because they're the baseline
The days where you earned nothing, shipped nothing, and just kept the lights on are the ones people hide — and they're the ones that make the eventual good day legible. If your log only contains wins, you can't see the shape of the work: the long flat stretch that the breakthrough sat on top of. Writing down the zero-days is what turns a pile of entries into a story you can actually read back.
6. End with the next tiny step, so tomorrow starts itself
Close each update with the one small thing you'll do next: "tomorrow: wire up the email form." It takes five seconds and it removes tomorrow's blank page too — you already know your opening move, so you don't have to re-decide from scratch. A log that always names the next step quietly becomes a to-do list that writes itself.
Cairn is a free daily log built to kill exactly this blank-page problem: it shows you a fresh writing prompt when you haven't posted yet, caps entries at a single honest line, and keeps your streak and all-time total so the ordinary days visibly add up. You can start your trail without signing up.