Why I'm Building in Public

Most portfolios are graveyards — a list of projects you finished years ago, sitting untouched while the real work happens elsewhere.

I wanted something different. A site that grows as I do, reflects how I think, and actually brings value to the people who land on it.

The constraints I gave myself

No templates. If someone can deploy the same site in five minutes, it isn’t a personal brand — it’s a theme.

Content first, design second. A polished empty site is still empty. Writing comes before polish.

Ship ugly, then refine. The worst thing is a perfect site that never launches.

What you’ll find here

Projects I’ve built across consulting, product, and open source. Writing on business strategy, technology, and the overlap between the two. Honest post-mortems on things that didn’t work.

If any of it is useful to you — even one idea, one framework, one honest mistake — then it’s worth publishing.

---

This is the first post. More to come.