In progress

Thought leadership · Enterprise architecture

The architect who codes — a new role without a name

For most of my career, architecture and engineering were treated as separate disciplines — one draws the map, the other builds the road. That gap is closing, and I think it's closing faster than most organizations realize.

This piece explores what that shift means for how we hire, how we structure teams, and what we should expect from the people sitting at the intersection of both. The best architects today can move fluidly between designing systems and implementing them. That's not a trend — it's becoming the expectation.

Status
In progress
Type
Thought leadership
Depth
Original thesis

Technical · Microservices

Why protobuf + gRPC changes more than your API layer

Most teams adopt protobuf to solve a serialization problem. What they don't realize is that contract-first design, enforced at compile time and shared across service boundaries, fundamentally changes how teams communicate — not just how services do.

This piece draws on years of hands-on experience with the tradeoffs, the patterns that work, and the ones that quietly create the chaos they were meant to prevent.

Status
In progress
Type
Technical + strategic
Depth
25 years of experience

How I approach writing

A note on process

"I write when I have something specific to say — rooted in a tradeoff I've watched organizations struggle with for years. The goal is never to add to the noise. It's to hand someone a clearer map of territory I've already crossed or carved out."

Ready to start a conversation?

Let's connect →