Engineering leader. I’ve spent two decades building software and the teams that ship it, and I write here about what that work is becoming in the age of agentic AI.
Over a little more than twenty years working across software and consumer electronics, I’ve worn most of the hats: engineer, technical lead, manager, founder, consultant, and (less typical amongst engineers) sales engineer and sales manager. I didn’t plan that range; I just kept following the interesting problem.
Those detours left me with a habit most engineering writing skips: looking at the business underneath the technology - why a product exists, what model pays for it, and how that quietly dictates the technical choices downstream. My background is in computer science and I stay hands-on; the teams I lead build with AI, agents, and modern tooling, and I care far more about what that changes in the actual work than about the noise around it.
A good share of what I write is about leadership itself: growing people, making decisions under uncertainty, and building teams that do their best work. Much of it has nothing to do with engineering - it’s the same craft whether you’re leading engineers or anyone else. I’m also interested in what it means to lead through this particular moment: what management means when your teams ship with agents, what holds, and what quietly breaks. If you lead engineers, or you’re trying to, I’m writing for you - concrete, honest, and grounded in work I’ve actually done.