On Building in Public

There's something uncomfortable about sharing your work before it's ready.

Most people wait until things are polished — until the project is done, the idea is fully formed, the code is clean. But I've come to believe that waiting until it's "ready" is often just fear dressed up as perfectionism.

Why Build in Public?

Building in public forces clarity. When you know someone might read what you're working on, you're forced to articulate it. You can't hide behind vague notes that only make sense to future-you.

It also creates accountability. Not the social media kind — the quiet internal kind. When you've told the world you're building something, there's a gentle pull to keep going.

The Real Cost of Waiting

The longer you wait to share something, the more attached you become to it. You've spent months on this thing. Now criticism feels personal. The feedback that could have reshaped the project early on now feels threatening.

Sharing early keeps you detached in the right way. You're not sharing your identity — you're sharing a draft.

What I'm Doing

I'm writing here as part of that practice. These are rough thoughts, not essays. They won't all be polished. Some will be half-formed. That's the point.

If something resonates, I'm glad. If it doesn't, that's fine too.

The act of writing is enough.