Who am I?

I started my career studying computer networking, planning to become a sysadmin. But while digging into routing tables and subnets, I also began teaching myself to code—just out of curiosity at first. That curiosity quickly became practical: I landed my first developer job while still in college, building full-stack systems with PHP, JavaScript, and MySQL.

As my career evolved, I found myself increasingly drawn to the kind of problems that exist at the boundaries—where architecture, security, and infrastructure meet. I moved into security-focused development, which sharpened how I approached software: every decision became a trade-off, every abstraction a potential risk surface. Security work taught me to think holistically, to see systems not just as functional but as fragile, and to design with failure in mind.

Eventually, I joined a company that needed someone who understood security and Kubernetes—and that brought me full circle. I’m now working in the DevOps world again, but this time with a broader lens: building Kubernetes-native solutions, writing Go, and solving problems that span security, infrastructure, and—ironically—networking, the very field I started in.

I suppose that makes me a DevSecOps engineer, though I care less about labels and more about doing the work well. I believe the best software is secure by design, not bolted-on later. I value simplicity over cleverness, and I think good systems are those that explain themselves.

These days, I focus on Go, Kubernetes, and Linux—building systems that are secure, reliable, and as simple as they can be. I write here to share the patterns I’ve seen in real-world infrastructure, and to explore how simple solutions lead to better, clearer software.