▶ REC00:00:00
back to writing
Building3 minMarch 15, 2026

Building in the Open

Why I share my work before it's ready, and what it costs.

Every time I publish something unfinished, a part of me dies a little. The perfectionist within screams. The ego cringes.

I do it anyway.

There's a certain magic in building in public. You make a promise to the void, and sometimes the void answers. You share an ugly prototype, and someone sees what it could become. You admit you don't know something, and someone teaches you.

The cost is real. People will see your failures. They'll watch you stumble. They'll form opinions based on incomplete information.

But the cost of hiding is higher.

When you build in private, you optimize for your own blind spots. You solve problems no one has. You polish features no one asked for. You emerge, years later, with something beautiful that nobody wants.

When you build in the open, reality intervenes early. Users tell you what's broken before you've built too much around it. Critics point out flaws you couldn't see. The market validates or invalidates your assumptions before they become expensive mistakes.

The ego cost of public failure is nothing compared to the opportunity cost of private perfection.

So I ship things that aren't ready. I write posts I'm not sure about. I share ideas before they're fully formed.

And yes, I cringe. But I also learn. And I build things that actually matter to people other than me.

That trade is worth it.