About me

I started writing code in 2011 on federal government case management systems. Not the most glamorous entry point. But it was rigorous work and it taught me early that software in the wrong hands at the wrong moment has real consequences. That stuck. Since then I've shipped production systems across energy, telecom, healthcare, and fintech. Each domain raised the bar in a different way. Healthcare taught me what reliability actually means when the software is sitting between a clinician and a patient. Telecom taught me distributed systems at scale. Fintech taught me that the blast radius of a bad deployment can be measured in millions. I've shipped across Azure, AWS, GCP, and PCF. Not by design. The work demanded it. That spread changes how you think about architecture. You stop treating any platform as the obvious answer and start asking what actually fits the problem. I also think most problems in software are actually people problems wearing a technical disguise. The architecture review that keeps getting pushed. The team that's slower than it should be. The system nobody wants to touch. Pull on those threads and you find something human underneath. That's what makes this work interesting. Everything on this page is free. I learn from every conversation. Book something if you have a real problem worth talking through.