Model Sprawl Is the New Tech Debt
AI teams accumulate models faster than they build controls. How to manage model sprawl with registries, drift monitoring, rollbacks, and consolidation.
The Room Before the Market
Anthropic did not just announce a model. It announced a room, and the real moat may be permission itself.
AI-Generated Code ≠ Safe Code
AI coding tools have genuinely made teams faster. The Harness 2026 State of DevOps report confirms it: AI coding adoption is up, velocity metrics are up, output is up. The same report notes that security and DevOps maturity haven't kept pace with the acceleration. More code is shipping,
When Your Gateway Has to Hold
A single agent handling predictable traffic is the easy case. Add a gateway, configure it correctly per Parts 1 and 2, and it works. The failure modes at scale are different in kind. An indirect prompt injection embedded in a document your agent was summarizing. A multi-agent workflow where a
Your Gateway Is Configured. Is It Working?
The gap between 'I added a gateway' and 'my gateway is actually working.' Four configuration decisions that separate coverage from false confidence.
The Quiet Substitution
What happens when your system silently substitutes and you don't find out until after you've acted on the result.
The Control Plane Your Agent Is Missing
An agent gateway is the infrastructure layer between your agent and everything it talks to. This is Part 1 of a three-part series on the control plane your agent is missing.
176 Days
What we spent, what we got, and the distance between possible and needed.
Treat Your Prompts Like Code
There's a category of AI bug that doesn't announce itself. The agent worked fine last week. Nothing in your codebase changed. No deployment, no model update, no infrastructure incident. But the output quality is worse, customer support tickets are up, and when you dig in, the
The AI Role That Doesn't Exist on Paper Yet
My job title is AI Solutions Developer. There was no listing. No hiring committee. The role didn't exist until I made it exist by doing work nobody else could do and proving it was worth formalizing. I think that's going to be the path for most
Stop Picking an Agent Framework by Feature List
The most common mistake developers make when choosing an agent framework is treating it like a software comparison article. They pull up a table of features, check off which framework supports memory, which has the cleanest API, which has the biggest community. Then they pick one and spend three weeks
What Nobody Tells You After "I Built an Agent"
The tutorials all end the same way. The agent works. It classifies the ticket, routes the email, summarizes the document. You run it a few times, it looks good, you ship it. Three weeks later it's hallucinating customer data at 2 AM, retrying in an infinite loop, burning