For years, the most honest part of my work happened in private conversations: with clients, with people I mentor, with teams I’m helping through a hard decision. This blog is an attempt to bring some of those conversations into the open, instead of leaving them locked inside a call nobody else sees.
This isn’t going to be a “10 tips for better leadership” blog, or textbook architecture theory. The idea is simpler and more stubborn than that: real trade-offs, the ones I discuss with clients, the ones I had to make myself when I founded and sold my own studio, the ones I keep seeing repeat in technical teams that outgrew their own structure.
It’s organized around the four themes I already use to think about my own practice:
- Architecture and technical decisions: real trade-offs, not blog dogma.
- From IC to leader: career and technical leadership.
- Founder lessons: building, scaling, and selling a tech company.
- The future of software engineering work: how AI is condensing roles that used to be separate.
If one of those is exactly the decision in front of you right now, this is a decent place to start. And if you don’t find the post you need here yet, write to me directly, it’s probably the next thing I’ll write about.