I build products, teams,
and the systems around both.
I spent a decade writing software; these days the job is deciding what to build, shaping how it's built, and looking after the people who build it. The writing here is me thinking through that work in public.
The work happens in four rooms of the same house: systems — architecture people can live in, with the decisions written down; product — deciding what deserves to exist and owning the outcome; people — teams designed with the same care as the software they run; and advocacy — good work, told well.
The journal
All writingLatest essay · Mar 15, 2026 · 3 min
What AI Tools In Education Actually Need
The most useful AI tools in education improve explanation, feedback, and access instead of turning learning into automation theater.
Developer Advocacy Should Ship Working Software
EssayDeveloper-facing teams build more credible content when their examples survive real implementation, not just polished demos.
Every Technical Role Is Now Product-Accountable
EssayAI is lowering the cost of building software. That does not remove the need for architects, managers, or technical leads. It removes the excuse for any of them to stay distant from user value.
The Cost of Unclear Ownership
NoteSmall Teams Have Never Had More Leverage
NoteThe Decision Hierarchy Problem
NoteThe Technical Leader in an AI-Accelerated Team
EssayAI tools speed up first-pass implementation, but leadership leverage is moving toward problem framing, system judgment, and team clarity.
How to Run an Architecture Review That Actually Helps
TutorialMake Decisions Legible
PrincipleProtect the Team's Attention
PrincipleIf you are shaping a product, a technical organization, or an architecture that has to survive contact with reality — those are the conversations I want more of.