Skip to main content

Engineering leadership for the real world

I have spent 30 years building things for the web — first as a developer, then as a technical director, and now as a VP leading engineering and architecture at scale.

These days I spend most of my time thinking about how teams actually work, why delivery systems fail, and why technology problems are almost never technology problems — they're almost always people, process, or time problems.

This site is where I collect practical thinking, opinions, and side projects in one place.

If you want the longer backstory, read more on the About me page.

Current focus

Right now I am thinking hard about how AI changes engineering organisations beyond the tooling layer.

That means looking at judgement, team structure, capability development, delivery pressure, and the uncomfortable fact that AI is moving faster than most organisations can adapt.

The interesting question is not simply how teams can ship faster with AI. It is how they can move faster without becoming more fragile or creating the kind of low-trust, high-debt systems that come back to bite them 6 months later.

We also need to consider the key leadership behaviours that either enable or undermine all of it.

If you lead engineering teams, think about how software gets built and shipped, or are trying to understand what AI actually changes about your organisation, you're probably in the right place.

Start here

The best place to start is the Thinking page, which brings together the themes I keep coming back to: speed, quality, judgement, capability, AI, and time.

Recent blog posts

Read all posts