Articles
Field notes from fourteen years of running infrastructure.
A small number of pieces, kept current. Each one answers a question I actually get asked, with the tradeoffs stated and the claims checkable.
-
The attribution problem, or why "just tag everything" fails
Tags are the standard answer to AWS cost allocation and they've never once been enough on their own. What a workable attribution layer actually looks like.
-
The state of CI/CD in 2026
GitHub Actions won by default, Jenkins won't die, and most pipelines are still slower and leakier than they need to be. An assessment from someone who runs this stuff.
-
The state of infrastructure as code in 2026
Terraform after the license change, what OpenTofu did and didn't become, why CloudFormation still runs more production than anyone admits, and what I'd pick today.
-
Your AWS bill is a design document
Cost work is architecture review with a forcing function. Opening a series on cloud spend with the method behind a $500K-to-$200K bill and ~$4M/yr held flat.