About

I’m an infrastructure engineer with nearly 20 years of experience keeping systems running. Data centres, virtual machines, networks, and cloud platforms. Whatever the workload runs on, the job is the same, make it reliable, make it secure, and make it something the next person can understand.

Most of my work these days lands on AWS, but I started long before the cloud was the default answer. Racking hardware, wiring networks, and running things on metal teaches you where the abstractions leak. That perspective still shapes how I design cloud systems now.

What I do

I help organisations design, build, deploy, secure and operate their infrastructure. That covers cloud architecture, Infrastructure as Code, networking, and the operational discipline that keeps a platform healthy once it’s live. I’ve worked across AWS, Azure, on-premise environments, and Kubernetes, often bridging the multiple.

Why I write

A lot of technical writing is either too shallow to use or so deep it forgets the point. I write for the people who have to build and run the thing, not pass an exam about it. Real problems, honest trade-offs, and what I learned from getting it wrong the first time.

Get in touch

Find me on LinkedIn.