I build and run infrastructure that stays up, and ship the software that runs on top of it.
Cloud and Azure systems by day. Independent products the rest of the time.
I am a systems engineer focused on cloud and Azure infrastructure. My work is designing, automating, and keeping enterprise systems available, secure, and recoverable.
Outside of the day job I design and ship my own products, and I run a small enterprise-grade lab at home to learn the hard parts of infrastructure first-hand rather than from a slide.
I am finishing an Executive MBA at Kennesaw State, on top of a BS in Information Technology with a concentration in Cyber Operations.
A four-node cluster I designed, racked, and run like production. A segmented VLAN network behind an open-source firewall, internal DNS with a primary and secondary resolver, full metrics and alerting, automated backups with a tested restore path, and public services exposed through an outbound-only zero-trust tunnel so nothing inbound ever touches the network. It is where I practice the enterprise patterns I use at work: segmentation, high availability, monitoring, and infrastructure as code. This very site is served from it.
A daily Japanese reading puzzle. One word a day: read the kanji, type the reading, keep the streak alive. The browser version is free, needs no install, and is served from the cluster above. The iOS app adds Endless mode and the full archive.
A mobile roguelike built around two inputs and no buttons: speak to cast your spells, tilt the phone to dodge. Survive as long as the void lets you.
A manual spending journal. No bank connection, no automatic imports, no subscription — the friction is the feature. Shipped, marketed, and rebuilt natively in Xcode after I hit the limits of cross-platform. I taught myself the full release pipeline end to end.
Open to conversations about infrastructure, cloud engineering, and interesting build problems. The fastest way to reach me is a short note here.