About

I’ve spent over a decade working in enterprise IT environments, mostly around keeping systems stable and operational under real-world pressure. A lot of that work was about reacting to issues, restoring services, and supporting production systems that couldn’t afford downtime.

Over time, I started paying more attention to what was happening underneath those problems — not just how to fix them, but why they were happening in the first place. That naturally pulled me toward infrastructure design, system behaviour, and reliability engineering.

That shift is what led me into infrastructure and platform engineering. It felt less like a career change and more like a change in focus: moving from “keeping systems running” to “designing systems that behave predictably when things go wrong”.

Most of my current work is hands-on. I spend time building and breaking systems in a homelab environment using Linux, Docker, Kubernetes, and networking tools — not in isolation, but as connected systems that resemble real production architectures.

The parts I enjoy most are usually not the tools themselves, but how they interact — how DNS decisions affect service routing, how reverse proxies shape architecture, how monitoring changes your understanding of a system once it’s visible.