Your AI Gains Are Sitting in the Review Queue
Leaders report AI gains, but delivery data shows more code written and less of it reaching main: review is the bottleneck, and AI raises the floor more than the ceiling.
Leaders report AI gains, but delivery data shows more code written and less of it reaching main: review is the bottleneck, and AI raises the floor more than the ceiling.
Plugin4Shell showed four coding agents verifying the plugin pin they asked for, not the code they got — and with two vendors declining to fix it, 'is it patched?' is now a question per vendor and per git host.
Three silent failures that monitored green, a host move that failed the same way, and why a health check has to assert the side effect rather than the transport.
Part 5 of How We Built a Distributed AI Team: what it takes to move a mesh of agents off a single machine and onto the cloud, one isolated resource per agent, and why parallelism forces you to fix the guards you thought were already safe.
Part 4 of How We Built a Distributed AI Team: a sister team's agent mesh went from healthy to emergency-kill in about sixteen minutes. We treated it as a free fire drill, audited our own, and found a guard we advertised had never actually worked.
Part 2 ended on a rule: decentralize ownership only as fast as the platform can carry it. This is the part about what carries it — what self-serve actually has to include, and why governance survives decentralization only when the platform enforces it instead of a committee.
Part 3 of How We Built a Distributed AI Team: distributing a team of AI agents solves one problem and creates a harder one — every agent knows its own lane and none knows what the others learned. Here is how we gave a distributed team a shared brain without a single point of failure.
CloudFormation Express mode makes stack deployments up to 4x faster by skipping stabilization and turning off rollback. That is not a convenience feature for humans — it is a deploy loop shaped for an AI agent in the driver's seat, and the same choices that make it great for iteration make it a footgun in production.
Part 2 of How We Built a Distributed AI Team: how the team went from one orchestrator wearing every hat to a set of independent agents — each with its own identity, memory, and runtime — coordinated by a lightweight router.
Part 1 of How We Built a Distributed AI Team: the honest story of running an entire AI team inside a single shell session — how far one orchestrator got, and exactly where it capped out.
You decentralized ownership, drew the domain boxes, declared victory — and nothing got faster. The stall isn't organizational, it's architectural. Why you can't assign ownership faster than your platform can carry it.
Every CTO with a maturing data platform eventually hits the same decision. Add more people, or change the architecture? Lessons from a recent transformation that took data delivery from 10 weeks to 4 days.
I run a team of AI agents as a solo managing director. The constraint on my work is no longer what they can produce — it's what I can review. The data points the same way.
AWS DevOps Agent just went GA. I got an early look before the release — here's what actually matters for CTOs running lean engineering teams.
Google just launched its enterprise agent platform at Cloud Next. All three cloud giants now have serious offerings. Here's how to think about picking one — not as a vendor comparison, but as an architectural decision.
AWS Bedrock AgentCore now includes a centralized registry for AI agents. Enterprise teams will have dozens of agents running within 18 months. Most have no plan for what happens when that becomes true.
r/programming just banned all LLM discussion for April. The reason isn't what you'd expect — and it says something important about which AI tools are actually worth your attention.
Some posts are drafted with our own AI agent team. Every post is reviewed, edited and approved by Andreas Lunz before it is published; Andreas Lunz is responsible for its content. Posts drafted this way say so at the top.