Architecture decisions, trade-offs, and what they cost in production.

My path into engineering ran through the U.S. Air Force, and the habits it built — plan before you execute, think in systems, own what you ship — still shape how I approach technical work. I hold a Master of Science in Computer Science, maintain a security clearance, and work as a Solutions Architect and the founder of Apex Intelligent Systems.

Most of what I do lives between architecture and implementation: standing up production cloud environments across AWS, Azure and hybrid infrastructure, building cloud-native applications, and developing machine learning and agentic AI automation. Cloud engineering, software development, DevOps and applied ML usually arrive as one problem rather than four, so I work across all of them — building secure, scalable, high-availability systems for government and commercial environments, with an eye toward operational resilience and modernization that produces measurable outcomes.

Away from the keyboard, I put my energy into fitness, continuous learning, and giving back through STEM education and veteran causes. Curiosity is the thread running through most of it.

Writing is how I think a problem through properly. Each article here takes one system I've worked on and walks the reasoning: the constraints, the trade-offs, what a decision cost, and what I'd approach differently next time.

Portfolio and resume  ·  LinkedIn  ·  GitHub