My friend and yours David Yanacek argues that harsh ops environments forge better engineers, same way Arrakis forges Fremen. This taxonomy of operational models - Frontline, SRE, DevOps, Platform - is the clearest breakdown I've read in a while, with the right amount of self-aware caricature. Worth your coffee break.

Google Cloud is rolling out actual hard spend caps for AI services that pause API traffic when you hit your budget. After years of telling customers "set a billing alert and pray," someone finally built the thing that stops the bleeding instead of just emailing you about it. Private preview, but promising. And now we all look silently but expectantly at AWS.

Coding agents are quietly rewriting the calculus of language choice. Simon Willison's short observation on technical lock-in captures something I've been chewing on: when an agent can port your app to React Native (or back), your language commitment looks less like marriage and more like a flexible lease. Worth two minutes of your time. Now I'm wondering about the cloud migration equivalent of this.

Spending eight figures annually on Google Cloud apparently still doesn't buy you a phone call before they suspend your account and vaporize your resources. Railway found out the hard way, and Simon Sharwood at El Reg has the painful play-by-play. Cloud concentration risk isn't theoretical when your provider treats you like a free-tier abuser. The tree of "Google is not a trustworthy partner to your company" must periodically be watered with the blood of customers, to quote Thomas Jefferson. He didn't like Google's approach to customer service, either.

Until now, if you wanted to know which team was setting your Bedrock bill on fire via InvokeModel, you got to guess. Converse had this at launch, InvokeModel gets it eighteen months later, and we're supposed to applaud "consistency." Your FinOps team's relief is matched only by their exhaustion. We are all so, so tired.

Pause and resume buttons for deployments, arriving in 2026. Truly the future is now. The 14-day timeout is suspiciously calibrated to "length of an average PagerDuty incident bridge call about why nobody approved the pause." Still, this is useful. I begrudgingly approve.

Larry Ellison and Andy Jassy holding hands in a Virginia data center is not how I expected 2026 to go, but here we are. The pricing model (port speed, not per-GB) is compelling.

Doubling the SCP limits is nice, but it's nowhere near sufficient for my needs. (Note: if I stop writing this item right here, I wonder how long I can string along conversations with the service team before they realize I'm trying to use SCPs as a database.)

Aurora MySQL finally ditched its bizarre 3.x versioning to match upstream numbers, which is to say AWS spent years confusing everyone before deciding that "the number on the box matches the thing inside the box" was actually a reasonable concept. The DBAs maintaining version translation spreadsheets can now retire them. The fact that DBAs have version translation spreadsheets proves my thesis: Microsoft Excel is a database.

AWS releases open source software that lets you run DynamoDB workloads on PostgreSQL, anywhere. Read that again. The company whose entire pricing model depends on you NOT leaving just handed you the escape hatch, wrapped it in Rust, and slapped Apache 2.0 on it. Someone in Seattle is having a very interesting Monday. I have authored a PR that adds Route 53 as a storage backend.

A 98% cost savings case study is a realization that the previous bill was 50x what it needed to be. This goes well beyond "we have improved" and into "what the HELL were you people doing before, checking your creds into GitHub?" Turns out compressing JSON before shoving it through a per-kilobyte pricing model works wonders. Shocking. Somewhere a Nine Entertainment engineer is wondering why nobody mentioned gzip existed before the bill arrived.

Six years into running AWS SDKs in production, and they're just now standardizing retry behavior? Jesus. The opt-in is available today, with defaults flipping in November 2026 - giving you only a few months to discover your application secretly depended on legacy mode's "retry until heat death of universe" approach. Ops teams, set your calendars.

CDK now has Mixins, because L1, L2, and L3 constructs apparently weren't enough construct types to confuse newcomers. Now you can compose abstractions across all three, which sounds great until you realize you're writing TypeScript to generate YAML to provision JSON to summon God. Somewhere, a Terraform user is laughing into their coffee. Laugh it up, Chuckles; there's no way you use Terraform regularly and don't adulterate that coffee with something stronger.

Remote code execution via a rogue server in the official Redshift Python driver. So your data warehouse client could become someone else's shell, which is a creative way to expand Redshift's feature set. Patch to 2.1.14, then go hug whichever security researcher caught this before your incident response team did.

Debug code shipped to production with no kill switch? Well that's not great. The "arn:aws-debug:file" scheme reading arbitrary files is the kind of feature that makes pentesters weep with joy. Patch to 0.2.1, rotate your secrets, and pour one out for whoever's reviewing that git blame.