I lead digital engineering at Guzman y Gomez in Sydney, where I'm responsible for four teams and the systems a national brand runs on.

I've been doing this for over 20 years. Long enough to have strong opinions, and long enough to know which ones to hold loosely. I started as an engineer who thought good architecture would solve everything. I now spend most of my time on the things architecture diagrams leave out — incentives, ownership, trust, and the slow work of making a team better than the sum of its people.

This is where I think out loud. Expect posts on scaling engineering teams, building product that survives contact with real users, AWS and platform decisions that age well, and the parts of leadership nobody warns you about.

I try to write the way I'd talk to a peer over coffee: specific, honest, and free of the consultant-speak that makes most engineering content forgettable.

If that's your kind of thing, follow along.

Opinions here are mine.