In brief

I wrote my first line of code at eight, and never really got the taste out of my mouth. Engineering is how I think, not just what I do. I ended up leading, which turned out to be a different craft rather than a promotion away from the old one: most of what I build now, I build with and through other people.

I lead a large team building business software at scale, and I have been at this for over twenty years, across telco, GDS, and software along the way. These days my attention goes to a few questions that keep compounding: how AI actually changes the way teams work, what an operating model should look like when the cost of building collapses, why asynchronous work is the default I keep defending, and where a human still has to make the call.

I have strong opinions, usually held loosely. I would rather be proven wrong quickly than right slowly, and I learn best in public, which is part of why this blog exists.

I write here in my own name, not my employer's. These are my views, worked out in the open, mistakes included. If something I wrote is useful, or wrong, I would rather hear it than not.

English is not my first language, and I use AI to help me write it. The ideas, the positions, and the judgment calls are mine. Which, if you have read anything else on this site, is more or less the whole point: let the machine handle the phrasing, keep the human on the part that actually matters.