My Story
For many years, I’ve been called a developer, a platform, network and wireless, infrastructure, DevOps and systems engineer, and many other kinds of engineers and experts! Honestly, I can be any of them, but none of them describes me. The one thing I’m really an expert in is breaking complexity down.
By nature, I’m a technical generalist. I like complex problems, but I hate complexity, and I hate manual, repetitive work. That’s why I’ve automated things wherever I worked.
I wrote my first program when I was 12, in GW-BASIC, and I’ve worked in IT for over 20 years. For the last 13+ I’ve run production systems where downtime had a real cost: national payment infrastructure, then incident command for a global high-availability platform. At one payment company, I took a critical platform from 84.6% to 99.5% availability. That work taught me to design for failure.
I’ve used AI every day since 2023, and I’ve been building with it on my own since 2024. It’s great at tasks, but the probabilistic nature of LLMs makes it hard to trust in production, so most of what I build sits around the model.
How I Work
- I read before I change anything.
- I break complex problems down before I build.
- If I have to do something twice, I automate it.
- I write down what I did and why, so the next person doesn’t need me.
My Philosophy
- If I can’t observe a system, debug it or recover it, it isn’t ready for real use.
- An agent near production doesn’t need blind trust. It needs boundaries, approval, and a way to show its work.
- Being reproducible is what makes a system trustworthy.