on building in public

There's a particular kind of anxiety that comes with sharing something before you think it's ready. I've felt it with every project I've shipped, every essay I've published, every repository I've made public.

The fear isn't really about criticism. It's about being seen mid-process — in that ungainly state between intention and execution.

But I've come to believe that the discomfort is the point. The work doesn't get better in isolation. It gets better in contact with the world, with friction, with the questions it generates in other people's minds.

Building in public is an act of epistemic humility. It says: I don't have this fully figured out yet. Come think alongside me.

The internet rewards finished things. Polished portfolios. Comprehensive tutorials. But the most valuable conversations I've had online started with someone sharing something half-baked — a rough idea, an early prototype, a half-formed question.

There's a craft to sharing early: being honest about what stage you're at, making it easy for people to understand the core idea, and remaining genuinely open to input rather than just seeking validation.

But the craft can't be learned in private. You have to ship.