Why I'm Finally Building in Public
After nearly two decades of building products behind closed doors, I'm opening up. Here's what changed, and why now.
For the better part of two decades, I’ve been building things. Digital products, teams, organizations, workshops. Thirty-six products at last count. Some succeeded. Most taught me lessons I couldn’t have learned any other way.
But here’s the thing. I did almost all of it quietly.
The Quiet Years
I prioritized family. I prioritized shipping. I prioritized the people on my teams over my own presence in the tech conversation. And I don’t regret any of that.
But somewhere along the way, I realized I had accumulated a massive backlog of lessons, patterns, mistakes, and insights that were just… sitting there. In my head. In Notion docs nobody would ever read. In slide decks from 50+ talks that lived on a Google Drive.
What Changed
Two things converged:
AI changed everything. Not in the “robots are taking our jobs” way, but in the “the entire craft of building software is being rewritten in real time” way. I’m living through this transition and I want to document it. The real version, not the Twitter hype cycle.
I ran out of excuses. The tools for publishing are better than ever. The cost of silence became higher than the cost of shipping imperfect writing.
What to Expect
This blog is where I’ll document:
- The building process. Real stories from shipping products, not sanitized case studies
- Team dynamics. What makes good teams tick (and what breaks them)
- AI in practice. How I’m actually using AI tools, not just theorizing about them
- Technical deep-dives. The kind of posts I wish existed when I was figuring things out
I’m not going for polished think-pieces. I’m going for useful, honest, and sometimes messy.
Let’s see where this goes.