Welcome
I’m a cloud architect who believes the best solutions are the ones you actually understand. After two decades building and securing mission-critical systems— from GPS command and control infrastructure to enterprise cloud platforms — I’ve learned that complexity is often a choice, not a requirement.
What I do: I design, build, and optimize cloud infrastructure on AWS. I automate the repetitive stuff so teams can focus on what matters. I translate business problems into technical architecture—and then build it, not just diagram it.
What drives me
The satisfaction of watching a deployment pipeline work flawlessly at 2 AM. The moment a Kubernetes cluster scales exactly as designed. Finding the elegant solution hiding inside the complicated one. Teaching someone something that clicks.
My Background in 30 Seconds
Now: AWS Senior Solutions Architect helping enterprises navigate cloud complexity
Before that: Led cloud engineering teams for DoD programs (Kessel Run, Army SMDC), built Kubernetes platforms on classified networks, ran cybersecurity operations
Started: Securing GPS command and control systems at Boeing, learning to balance mission requirements against security constraints
Expect
Deep dives into cloud infrastructure — Kubernetes on bare metal, WordPress deployments that don’t suck, OCI vs AWS comparisons, Alpine Linux in production, Cloudflare Workers edge computing.
Real-world automation — CI/CD pipelines, infrastructure as code, PXE boot setups, configuration management that actually works in practice
Lessons from production — What I learned when things failed, how I debugged the weird issues, the trade-offs nobody talks about in the documentation
Side quests — 3D printing optimization, home lab experiments, truck modifications, local LLM integration, whatever rabbit hole I’m currently down
I write for the person who wants to understand how things work, not just copy-paste commands. You’ll get context, reasoning, and the occasional “here’s what I’d do differently next time.”
Philosophy
Build things that work. Not things that look impressive in a slide deck. Not things that require a PhD to maintain. Things that solve the problem, stay running, and make sense when you come back to them six months later.
Automate thoughtfully. Automation for automation’s sake is how you end up with brittle systems nobody understands
No posts were found.