ABOUT ME

I've been in infrastructure long enough to remember when 'cloud' meant something you hoped wouldn't rain on your physical servers. I started as a NOC engineer watching provider-scale networks, spent years as a sysadmin keeping bare metal alive, and somewhere in that journey fell in love with the problem of making complex systems predictable. Not just keeping them running — making them understandable.

What actually drives me is the feedback loop between code and production. The moment an engineer pushes a change and knows — really knows — it landed safely, with visibility, with a rollback path, inside a platform that doesn't fight them. I care about that experience. Building it well is harder than it looks and more satisfying than almost anything else in this field.

Right now I'm deep into the intersection of platform engineering and AI. Not AI as decoration, but using it to compress the operational work that still consumes too much human attention — automating runbooks, surfacing patterns in observability data, building agents that handle the boring parts of a release. The underlying problems haven't changed. The tools have gotten genuinely interesting.

This site is my logbook. I write here about things I'm building, patterns worth remembering, and rabbit holes that turned out to be worth following. It's not a polished portfolio — if you want the full credentials, grab my CV. This part is for the craft. If something here saves you a debugging session or puts a name to a pattern you've been living with, that's the goal.