St. Patrick's Day Special: Luck Had Nothing to Do With It

Six months ago I started posting more openly about what I'm building, how projects are going, and what I'm learning. Here's an honest accounting of what that's done (and not done).

What changed

Accountability. The biggest practical effect has been accountability. When you say publicly that you're going to ship something, you're more likely to ship it. Not because anyone is watching closely — they're usually not — but because the act of stating it changes your relationship to it.

Clarity of thinking. Writing about a problem forces you to understand it well enough to explain it. I've caught conceptual gaps in my own understanding more times than I can count by trying to write a post about something I thought I knew.

Inbound conversations. Not clients, exactly — more like peers. People who are working on similar problems, or who've already solved something I'm struggling with. That network has been genuinely useful.

What didn't change

Traffic. Building in public is not an SEO or traffic strategy on its own. A handful of posts and some social shares don't move the needle unless there's consistent volume and the content is genuinely useful.

Revenue, directly. I haven't been able to trace a single client directly to a public post. Some indirect credibility effect, maybe. Nothing measurable.

The things nobody tells you

Most people don't read carefully. They scan. If you're writing long-form technical content, the audience is small and specific. That's fine — small and specific can be valuable — but calibrate your expectations.

Consistency matters more than quality. A mediocre post published beats a great post that never ships. I've spent too much time polishing things that would have been fine 40% rougher.

You will cringe at your early posts. That's correct. That means you've learned something. Don't delete them.

Is it worth it?

Yes, but not for the reasons I expected. The compounding value isn't in the posts themselves — it's in the thinking they force you to do, the relationships they occasionally start, and the record of what you were working on and why.

If you're building something, you should probably write about it. Not for the audience. For yourself.