I like solving problems, especially the ones where engineering and security meet.
For most of my career I've worked closely with platform teams and developers, building the platform services they depend on. The goal has always been the same: a platform that doesn't block developers, but lets them ship faster and more securely. I've built these platforms on-prem on bare metal and on every kind of cloud, from the big hyperscalers to smaller providers.
I'm an old pentester at heart, and I've worked both sides of security. I've written iptables rules and Snort signatures to keep attackers out. I've also written scanners and inspected traffic to find my own way into applications. That background shapes how I build: I know how systems get broken, so I know where to put the defences.
As a security professional I cover the whole compliance path, from securing the platform and the applications to writing the policies that turn security practice into compliance work. I believe compliance belongs in the foundation and in everyday practice, not in a binder that comes out once a year. Build it into the base, and security can grow from the ground up. That includes working hands-on with developers and platform teams to build security into what they make.
To me, a security practitioner's job is to help. Developers and everyone else should be able to work as easily as possible and as securely as possible, with security clearing the way rather than standing in it.
I use AI tools every day. They run as a dark factory that turns planned work into pull requests, and they work next to me as an assistant. Together they let me get more done than ever before.
I wrote the book Ubuntu System Administration Guide (BPB Publications, 2025): a hands-on guide from the first Ubuntu install to Kubernetes and CI/CD on your own servers.
I host the DevSecOps Talks podcast, run a small cluster at home that is more production than it should be, and fly drones that turn fields and forests into maps. This site is where I write it down.