I build and run Azure infrastructure. Nine years of it, most recently across a twenty-service Kubernetes platform.
BS in Information Technology, University of West Florida, 2017, with a Global Cyber Alliance project testing DNS response policy zones on AWS.
AKS, Helm, NGINX Ingress and Gateway API, Container Apps with .NET Aspire. Right-sizing driven by measured usage.
Azure DevOps YAML multi-stage pipelines, GitHub Actions, Release Flow branching, and branch policy that makes the path from work item to production auditable.
Terraform and Bicep, including how modules find and call each other once a repository has hundreds of files.
Application Insights with distributed tracing, KQL dashboards, consumption tracking for AI workloads, and the cost work that follows from being able to see usage.
WAF traffic analysis across Azure Front Door, dependency remediation with Sonatype IQ, Entra ID, Intune, and RBAC built to survive an audit.
PowerShell, C#, Python and Bash. Ticketing automation, ETL into Snowflake, and a Copilot extensibility framework used across 30+ repositories.
A plain English explanation for people who know technology but do not work in it, built around the Terraform that puts this site on the internet. It quotes its own source and walks through it line by line.
ClicktrackA rhythm game that builds its own charts. It runs live onset detection on whatever audio you share from a browser tab, so it plays along to your music, with no backend and no build step.
Module references, Bicep and TerraformThe practitioner counterpart to the infrastructure page. How modules reference each other at scale in both languages, and the failure modes that only appear once a project is large.
Fifteen games and a leaderboardTetris, Snake, Minesweeper, Asteroids and nine more, running in the browser on the same free static web app, with a shared leaderboard behind one small function.
Static files on Azure Static Web Apps, described entirely in Terraform and deployed with one command. It costs nothing a month to run. The only resource on the bill is a storage table holding a few kilobytes of game scores, which prices out below a cent.
The infrastructure page prints the file that created the thing you are reading it on. The whole site can be destroyed and rebuilt from that file in about a minute.