Choose a release
Start with a concrete milestone rather than a vague desire to post.
'/%3e%3cpath%20d='m21%2023.3%2010-5.7%208%204.5-10%205.8%2014.2%207.9v6.6L31%2049.5l-8-4.6%2010.1-5.8L19%2031.2v-6.7l2-1.2Z'%20fill='%23fff'/%3e%3c/svg%3e)
Build in public calendar
Share concrete progress without manufacturing a founder persona.
Use releases and repository changes to create honest build-in-public posts about decisions, tradeoffs, lessons, and product progress.
For developers and founders who want to communicate consistently without turning every day into performance art.
maker/quietship
Latest releasev0.6 — Restart-safe background jobs
Repository context becomes an editable campaign—not an automatic publish.
The problem
“Build in public” becomes noise when the work disappears.
Generic progress posts say that work happened but give readers nothing useful to learn or discuss.
Writing from memory strips away the technical detail that made the decision interesting.
Constant posting pressure rewards volume instead of honest, relevant communication.
The workflow
Let shipped work supply the evidence.
Confirm what matters
Describe the audience, product goal, and lesson that source material alone cannot infer.
Generate varied stories
Mix release facts with implementation lessons, tradeoffs, questions, and next steps.
Publish at a sustainable cadence
Use the calendar to spread meaningful progress instead of forcing daily filler.
Example output
One release. Three useful angles.
maker/quietship · v0.6 — Restart-safe background jobs
01Progress
QuietShip v0.6 makes background renders restart-safe. A deploy can interrupt a worker without losing the job or producing duplicate output.
02Lesson
Queues are not the source of truth. In v0.6 the database owns render state, while the queue only wakes a worker. That made duplicate signals harmless.
03Next step
Restart-safe jobs are shipped. The next constraint is observability: showing users enough progress without exposing the machinery.
What changes
Less blank-page work. More deliberate communication.
- More concrete progress posts
- Technical lessons preserved
- Less pressure to publish filler
- A sustainable calendar
Questions
Practical details.
Will every post sound like an announcement?
No. The calendar deliberately mixes announcements, lessons, benefits, tutorials, and discussion prompts.
Can I remove technical details?
Yes. Every draft is editable, but preserving one concrete detail usually makes the story more credible.
Do I need a new release every week?
No. One release can support several posts over multiple weeks, and repositories without releases can use README and project context.
Use the repository you already have
Generate the first three posts now.
No signup for public repositories. Preserve the result when you are ready to build the full calendar.