Why I Build in Public

Building in public isn't about marketing. It's about accountability.

When I share what I'm working on — even half-finished stuff — it changes how I work. I think more clearly. I write better code. I actually finish things.

There's something about knowing someone might see your work that raises the bar just enough.

It also creates unexpected connections. People reach out with ideas, feedback, or just to say they found it useful. That's the best part.

You don't need an audience to build in public. You just need to hit publish.

A few rules I follow: - Share the process, not just the result - Be honest about what's broken - Don't wait until it's perfect - Write for yourself first

The worst case is nobody sees it. The best case is it helps someone — including future you.