On Building in Public

There’s a strange pressure that comes with making things on the internet. The temptation is to disappear into a cave, emerge months later with something perfect, and hope the world notices. But I’ve found the opposite to be more rewarding — and more honest.

The messy middle is the real story

Nobody remembers your launch tweet. What sticks is the journey: the half-baked prototype you posted at 2am, the bug that took three days to find, the pivot that felt like failure but turned out to be the best decision you ever made.

When you build in public, you give people permission to be imperfect too. You create a trail that others can follow — not a highlight reel, but a map with all the dead ends marked.

Why it matters for indie makers

As solo builders, we don’t have marketing departments or PR teams. Our authenticity is our distribution. When you share your process, you’re not just documenting — you’re building trust, one commit at a time.

The tools we build are extensions of how we think. Showing the thinking, not just the output, is what turns users into collaborators and strangers into community.

A commitment

This space is where I’ll share the unpolished thoughts, the works-in-progress, and the lessons learned from building tools that matter. Not because I have it figured out, but because figuring it out in public is the whole point.