Lead Engineer · Sydney, Australia
Designing systems that last, and teams that can own them.
I write about resilient distributed systems, the engineering judgment that keeps them safe now that AI makes code cheap, and leading the engineers who build them. Drawn from building and modernising enterprise platforms where mistakes are expensive.
Product R&D at a CMS vendor · global digital agencies · regulated enterprise. Now leading engineers through AI-assisted delivery.
Australia · Italy · Malaysia · Bangladesh
Now Automating environment refreshes with scoped identities and pipeline approvals, and leading two squads through AI-assisted delivery.
Three areas I work in
All articles →Systems fail at the boundaries: ordering, timing, retries and who owns the data. I write about designing for those failures before production finds them.
Start withLast write wins, and the customer loses3 articles →Safety is a permissions problem before it’s an approval problem. Agents, guardrails and review, where mistakes are expensive.
Start withHuman-in-the-loop is not a security boundary2 articles →Making good decisions possible without being in every one: ownership, honest feedback, and judgment that grows in the team.
Start withTech debt snowballs, then it avalanches3 articles →Also: 8 notes on what I'm reading, a bookshelf, and 15 earlier Sitecore & .NET posts.
Recent articles
All articles →2026
- Human-in-the-loop is not a security boundaryAI delivery8 min read
- Tech debt snowballs, then it avalanchesLeadership5 min read
- Deep Work, read as a lead engineerLeadership · Review3 min read
- Don't build business logic on an expiry notificationSystems4 min read
- Last write wins, and the customer losesSystems3 min read
- Release risk usually isn't in the codeSystems3 min read
- Being right is not the jobLeadership · Review2 min read
- Moving my blog off WordPress with an AI agent: what I delegated, and what I didn'tAI delivery4 min read