Exploring the echoes reverberating through time left by the technology of yesterday as we embrace the technology of tomorrow.
Every platform team buries the business in an eighty-nine-row YAML and calls it self-service. That isn't self-service, it's a configuration handoff. Decisions as Code is the discipline of extracting the five decisions that actually matter and letting the platform absorb the rest.
Twelve months of running agentic coding tools daily, and the failure mode that keeps repeating isn't the dramatic one. It's the quiet one, the agent doing the thing it was asked, exactly, to a result nobody wanted.
GPT-5 dropped this week. The benchmark deltas are real, the marketing layer is loud, and the question for shops with already-working AI stacks is which routing decisions actually need to change. Honest answer: fewer than the launch suggests.
Eleven seconds, very thorough, immaculate audit trail. A walk through what one Tuesday afternoon in my homelab teaches you about working with agentic coding tools, and the workflow changes that follow.
AWS shipped its own agent SDK two weeks ago, joining LangGraph, Semantic Kernel, the OpenAI Agents SDK, the Anthropic Agents SDK, and a half-dozen others. The question isn't which one's best. It's whether the framework layer is still where the differentiation happens at all.
It isn't a cluster in the data-center sense. It's a small, deliberate setup, a Mac Studio for inference, a Mac mini for the always-on services, fast portable SSDs at the working ends, and a real NAS underneath. Worth being honest about what it is and what it isn't.
Agents that run for ten minutes mostly work. Agents that run for ten hours mostly don't. The middle is where the actual production work lives, and the patterns we have for it are weaker than the conversation pretends.
Two years into agents-everywhere, a small set of design patterns has separated from the noise. Worth being explicit about which shapes are actually paying back in production and which are still mostly aspirational.
A day after Claude 4 landed, the math is starting to settle. Opus 4 has its place. The honest read is that Sonnet 4 closes enough of the gap that the price-for-marginal-capability case for Opus needs more justification than I've been giving it.
Anthropic shipped the new model family yesterday. Opus 4 is the new top tier; Sonnet 4 is the everyday workhorse. After a day on real work, what's actually different and what isn't.
Google's I/O was Gemini 2.5 Pro getting a clean coming-out and the agent story finally being told with a straight face. The model is real. The agent story has more work to do than the keynote suggested.
Build was the agents conference Microsoft has been preparing for. The agents pitch lands. The governance story underneath it is exactly as unfinished as it was a year ago, and the contradiction is starting to show.
