Principal Cloud Solutions Architect
I don't deploy resources. I build platforms.
A teenager in his dad's medical clinic. The computer system crashes. Patients waiting. I pick up the phone, talk to tech support, and fix it myself.
In that moment, I felt it — the rush of solving what others couldn't.
" I knew then. This is what I was meant to do. "
First year of college brought a diagnosis: dyslexia. For most, a setback. For me, a revelation.
While others memorized protocols, I visualized them — watching a packet of data traverse routers, descending through the TCP/IP stack from Application to Physical.
This wasn't a limitation. It was a different operating system. One optimized for pattern recognition. For systems thinking. For seeing the whole architecture at once.
Unless you're in a submarine or a classified bunker, your infrastructure belongs in the cloud. I saw this in 2010. The market caught up.
Clicking around the Azure portal isn't engineering — it's gambling. One misclick. One forgotten setting. One undocumented change.
Every firewall rule. Every network path. Every policy. Defined in code. Reviewed in PRs. Deployed through pipelines. Reproducible. Auditable. Real.
Numbers don't lie.
I write about what I learn in production.
Autonomous AI trading agent — architecture, Kelly sizing, and real-money lessons
Lessons from managing 1,200+ files of Bicep IaC across 6 spoke networks
How I built multi-layer safety guardrails to ensure it never happens again