What I do
Done well, it's nearly invisible. You feel it in the absence of confusion, in systems that scale as intended, in teams that aren't fighting the tools they work with.
Three areas of work
The role of trusted advisor is one I've earned — through years of deliberate investment, late nights, and a commitment to understanding not just the technology but the business context it has to serve. I help leadership navigate ambiguous problems, weigh build vs. buy decisions based on cost, ROI, and time-to-market, and identify the right tool for the right job — not the most fashionable one.
I build reference architectures, clear technical obstacles, and delegate based on team strengths. When cycles allow, I write working code — design patterns that teams can follow and that compress the path from architecture to delivery. Keeping a pulse on emerging technologies is core to this work: knowing what exists, what's ready, and what's hype is how you make decisions that age well.
I believe we're at an inflection point. The gap between engineering and architecture — once wide — is collapsing. The best architects today can move fluidly between designing systems and implementing them. That's not a trend. It's becoming the expectation. I've lived on both sides of that line, and I think that's exactly where the most valuable work happens.
A thesis
"A collapsed gap between engineering and architecture — a single, fluid mindset. This is a new role which does not yet have a name."
The expansion is good when there are available cycles. Too much pulls the architect away from observing the system holistically — and chaos, left unobserved, leads to complexity and technical debt that compounds quietly until it can't be ignored.
How I lead
Decisions are made with a committee of trusted advisors and empirical facts — inclusive but decisive. People know where they stand and why.
I measure success by how little the team needs me to function well. I lean on individual strengths and mentor toward balance and growth.
Every conversation, every decision, every architecture review starts with the same question: what is the value we are trying to deliver, and are we doing that without increasing chaos?
I ask the same of the people I work with — come prepared so we can make our time together count. Constructive time is a shared resource worth protecting.
Technologies and platforms
Want to see this thinking applied to real work?
See featured work →