Tags: discuss, startup, beginners, career

The first time I tweeted about my project, I sat with the draft open for forty minutes. I rewrote it six times. I hovered over the "Post" button and felt actual physical nausea. This is a grown man who has given presentations to rooms of two hundred people, who has defended architecture decisions to CTOs, who once handled a production outage during a Super Bowl ad campaign. But posting "Just shipped the first version of my AI automation tool" to an audience of maybe eighty followers — that broke me.

I posted it anyway. Nobody cared. Two likes. One reply from a bot. The world did not end.

That's the dirty secret of building in public: the fear is real, but the risk is imaginary. Nobody is paying that much attention to you. Especially at the beginning. And that's actually the superpower.

Here's what I've learned after months of building in the open: the vulnerability isn't a side effect of the strategy. The vulnerability is the strategy.

When I started writing honestly about my numbers — zero users, the embarrassing bugs, the features I spent three days on that nobody asked for — something shifted. People started reaching out. Not in droves, but one by one. Someone who had the exact same problem with webhook reliability. Someone who had tried building a similar tool and failed. Someone who just wanted to say "I'm on the same journey, keep going."

Those connections are worth more than any polished landing page. They're real. You can't buy them with ads. You can't SEO your way into them. You can only earn them by showing up consistently and being honest about where you actually are, not where you wish you were.

The counterintuitive part: sharing your failures builds more trust than sharing your wins. Everyone posts about their Product Hunt launch. Almost nobody posts about the three months of silence before it, when they were questioning every life choice and their GitHub contribution graph looked like a flatline. When you write about that part, you're not just documenting. You're giving permission. Permission for other builders to be in the messy middle without feeling like they're failing.

I've had to learn where my line is. I share revenue numbers now — the real ones, not the "we grew 300% month over month" vanity metrics. I share technical decisions and why I made them. I share the emotional roller coaster. What I don't share: anything that would compromise user data, anything that would burn bridges with past employers, and anything that's still too raw for me to talk about with clarity. You need boundaries. Public doesn't mean boundaryless.

The accountability piece is real too. When I committed publicly to shipping one feature per week, I suddenly had a reason to finish things that I might have abandoned at 80%. Knowing that a handful of people would notice if I didn't ship — that tiny bit of social pressure — was often the difference between shipping and drifting.

Would I recommend building in public to everyone? Honestly, no. It's not a magic growth hack. It's slow. It's uncomfortable. It takes months before you see any return. But if you're already building alone and you're already documenting your journey anyway, making it public costs almost nothing and opens doors you didn't know existed.

The fear doesn't go away. I still get nervous before hitting publish. But I've learned to recognize that feeling as a signal: if I'm scared to post it, it's probably the right thing to post.

The real, messy updates continue at xundao.xin.