Latest blog post
Code Tennis is Why AIDD Stalls
Why AI-driven development stalls when teams improve code generation without improving coordination, handoffs, and governance.
The courier problem in early AIDD
The problem with early AIDD was never just code quality. It was the human loop turning into a courier service instead of a delivery system.
When an engineer keeps serving problems to a chatbot, receiving code back, pasting errors in, and repeating the loop, the work starts to resemble code tennis rather than engineering. The human stays in the loop, but often in the weakest possible role.
What actually limits progress
Research has long shown that engineers don't spend most of their day typing code. The real work lives in clarification, trade-offs, testing, review, and coordination.
That is why the biggest gains don't come from faster snippet production alone. The real question is whether the workflow lets planning, implementation, review, and iteration move together with clearer roles and better handoffs.
Why leadership should care
If software delivery becomes more orchestration-heavy, leadership has to invest in structure as well as speed.
- Clear roles
- Clear handoffs
- Clear quality gates
- Clear governance over data, testing, and release
The winners won't just generate code faster. They will coordinate better, review better, and make accountability visible.