I'm going hard today. Collating over 100 recent articles on the FinOps space and aggregating them down to a handful of select topics, this one stood out to me like a sore thumb, screaming for attention. This is going to be a bit longer than normal. Breaking News:

I built a system at Adobe called Spot Stack. It was tiered infrastructure provisioned by Auto Scaling Groups (ASGs) that delivered EC2 resources to a pre-Kubernetes container platform. It managed capacity well, and did so at the lowest cost possible. Inevitably, Auto Scaling groups improved, rendering the system I built

I've never been woken up at 2am because of Spot. That needs context, because without it, it sounds like a brag. I've been paged plenty. Or called. Pagers are a bit dated. You get the point. Editing configs on an HA pair that triggered immediately. A

Posted another video this week. It’s a double-continuation; it dives deeper on the previous video I posted and continues the FinOps thread I’ve been focussed on this month. Figured I’d post the transcript for those of you on United flights without headphones so you don’t get

AWS says Graviton4 delivers 30% better performance than comparable its previous generation. That number is real under the benchmark conditions AWS used to generate it. The more honest question is what “30% better performance” means for your workload under your traffic conditions. No spec sheet can answer that. The architectural

Build errors show up in your terminal in seconds. Cost errors show up in your budget four weeks later. By then the architectural decision that caused the overspend is three sprints old, merged, deployed, and running in production. You're not going back to change it. This is the

I woke up this morning, made coffee, and sat down at my balcony overlooking the tranquil Andes here in Quindio; hell, for all I know the coffee I’m drinking was grown directly across the valley in clear view every morning. You can’t blame me for smiling. Over the