Building in Public: What 30 Days Taught Me About Showing Up

The One Rule

Ship something visible every day. That was the whole rule. Not "work on something," not "make progress." Ship. Make it visible. Do it in public.

I set that rule for myself at the start of May and held it for 30 days. Some days the thing I shipped was a post. Some days it was a commit. Some days it was a voice memo I uploaded to SoundCloud at 11:47pm because I'd spent the whole day on the wrong thing and needed something to count.

I'm not recommending that last part. But I'm also not pretending it didn't happen. This is what a month of building in public actually looks like.

What Broke

Perfectionism

Day four. I had a post three-quarters written that I liked. I wanted to finish it properly. But "properly" would have taken two more days, and the rule said ship today. So I published what I had, clearly marked as a draft in progress.

Nobody noticed it was incomplete. Two people replied to say it helped them. The version in my head, the one that would have been perfect, never would have reached them.

Perfectionism is a form of hoarding. You accumulate finished things that no one can use instead of shipping useful-enough things that people can actually do something with.

Energy

Week two was the hardest. Not because I ran out of ideas. Because I ran out of the specific energy that creative work requires. Not tired, exactly. Scraped. The kind of hollow you feel when you've been producing without replenishing.

What I learned: building in public without any private time to think, read, and refill doesn't work. You can't sustain output that has no input behind it. The ratio matters.

Scope

I kept starting things too big. A full tutorial. A detailed breakdown. Something comprehensive. Those aren't daily-ship things. They're weekly things. Learning to scope down to the smallest valuable unit took most of the month.

What Stuck

"Showing up every day, even badly, builds something that showing up occasionally can't."

Feedback loops

When you ship slowly, feedback arrives slowly and you can't tell what caused what. When you ship daily, the signal gets tight. You can see which things land. You can feel the difference between a post that resonates and one that goes quiet. Over 30 days, that feedback is a real education.

Momentum

This one surprised me with how physical it felt. There's an actual weight to having shipped something today. Not smugness. More like ballast. You feel more solid in the work. The streak itself becomes a reason to keep going that's separate from whether any individual thing was good.

Accountability without an audience

I don't have a massive following. Nobody was watching with their arms crossed, waiting to see if I'd fail. But I was watching. And it turns out that's enough. Declaring in public that you're doing a thing creates accountability to the version of yourself who said it.

The Surprise

I expected to get better at shipping. I did. But the thing that actually changed was my relationship with being seen.

I used to over-qualify everything. Hedge constantly. Announce caveats before the idea even landed. "This might not work for everyone" and "I could be wrong about this" before I'd even made the point. It's a form of pre-emptive apologizing, and it makes everything you say smaller before anyone has a chance to disagree with it.

Shipping every day removed the option to over-qualify. There wasn't time. You say the thing, it goes out, you find out what happens. After a month of that, the over-qualifying felt less necessary. Not because the ideas got better, but because I got more comfortable with the fact that some of them would be wrong and that was fine.

The Real Cost

Nobody talks about this part: building in public costs you the right to quit privately.

When you build privately, you can stop at any point and nobody knows. The project lives in a folder, the idea lives in a note, and you can walk away without explanation or judgment. That's a real comfort, and it's one you give up the moment you start sharing.

When you stop building in public, people notice. Not in a dramatic way. But they do notice. And you notice them noticing. The accountability that drives you forward also raises the cost of stopping.

That's not a reason not to do it. But it's worth knowing before you start. Building in public is a commitment, not just a strategy. Treat it like one.

"The cost of building in public is that you can no longer pretend you haven't started. That's also the point."

Start Smaller Than You Think

If you want to try this, here's the only advice I have: whatever you're planning to ship, cut it in half. Then cut it in half again. What's left is probably closer to the right size.

Not because small things are better. Because small things can actually be finished in a day. A finished small thing is worth more than a never-finished big thing at any ratio.

• A note is a post. One observation, one paragraph. That's enough.
• A question is a post. Something you're genuinely trying to figure out, asked in public, is useful content.
• A failed thing is a post. What you tried, what went wrong, what you learned. This is often the most valuable thing you can ship.
• A work-in-progress is a post. Label it clearly and share it anyway. People don't need finished. They need honest.

Start with one thing, visible, today. Not a strategy session about how you'll do it. Not a content calendar. One thing. The rest figures itself out from there.