Why I Started Building in Public

There's a version of me that would have waited until everything was perfect before showing anyone. Clean code, polished UI, thorough documentation. Only then would it be worth sharing.

That version shipped almost nothing.

The problem with waiting

Waiting for "ready" is a loop. You finish one thing, find something else that needs work, fix it, and find three more. The project never leaves your hard drive.

Shipping something rough forces a different kind of thinking. Instead of asking "is this good enough?" you ask "what does this actually need to be useful?" Those are very different questions.

What building in public does

• Accountability. If I said I'd ship something, it's out there now. I can't quietly drop it.
• Early feedback. Real users catch things no amount of solo review will surface.
• Learning in the open. When I write about a problem while solving it, the writing sharpens the thinking.

The uncomfortable part

You'll ship things that aren't great. Someone will point it out. That's fine — it's a faster feedback loop than shipping in silence and never knowing.

The work gets better. So do you.