Most people hide their work until it's perfect. They work in private, polish everything, and only share the finished product. I used to do that too. But I think it's a mistake.
Building in Public Makes You Better
When you build in public, you're accountable to more than yourself. You can't quietly quit. You can't hide behind perfectionism. You have to ship, iterate, and improve-because people are watching.
That pressure is a feature, not a bug. It forces you to show up consistently. To finish things. To put work out into the world even when it's not perfect.
You Learn Faster
Building in public means you get feedback early. Real feedback from real people-not just your own head telling you something needs to be perfect before you ship it.
You find out what resonates. What people actually care about. What's valuable versus what you *think* is valuable. And you adjust.
It Builds Trust
People don't trust polished perfection anymore. They trust authenticity. They trust the journey. When you build in public, people see the work. They see the struggle. They see you figuring it out.
That's more valuable than a perfectly polished final product that appeared out of nowhere.
The Risk Is Overstated
"But what if people steal my idea?" Cool. Let them try. Ideas are cheap. Execution is everything. And if you're building in public, you're ahead because you're actually doing the work while they're still thinking about it.
"But what if I fail publicly?" Good. Fail fast. Learn. Adjust. Build again. That's how you get better.
How I'm Doing It
This site. This journal. The Odds philosophy. I'm building all of it in public. Sharing the process. The wins. The mistakes. The pivots.
Because I'd rather build something real with people following along than hide until it's "perfect" and never ship.
If you're building something, consider doing it in public. It's uncomfortable. But that's the point.
Build in public. Ship fast. Iterate. Repeat.