The Mythical Agent-Month
The article reflects on how AI agents are transforming software development, drawing parallels to Fred Brooks's 'The Mythical Man-Month' and questioning whether lessons from past software engineering challenges still apply. The author describes a new work pattern involving AI agents that increases productivity but introduces risks like code bloat, technical debt, and coordination issues. He emphasizes the continued importance of human oversight in maintaining software quality and conceptual integrity despite advances in AI-driven development.
- ▪AI agents are changing how developers work, often disrupting sleep and traditional workflows.
- ▪The author uses tools like roborev to supervise AI agents and maintain rigor in agentic software development.
- ▪Brooks's Law and Conway’s Law are re-examined in the context of AI agents, raising concerns about scalability, coordination, and system design.
- ▪An 'agentic tar pit' is described, where AI-generated code leads to increased complexity and technical debt.
- ▪A working program is only a fraction of a complete software product, and AI agents often fail to address the full requirements of production-ready systems.
Opening excerpt (first ~120 words) tap to expand
The Mythical Agent-Month ai agents thoughts Author Wes McKinney Published February 17, 2026 Like a lot of people, I’ve found that AI is terrible for my sleep schedule. In the past I’d wake up briefly at 4 or 4:30 in the morning to have a sip of water or use the bathroom; now I have trouble going back to sleep. I could be doing things. Before I would get a solid 7-8 hours a night; now I’m lucky when I get 6. I’ve largely stopped fighting it: now when I’m rolling around restlessly in bed at 5:07am with ideas to feed my AI coding agents, I just get up and start my day. Among my inner circle of engineering and data science friends, there is a lot of discussion about how long our competitive edge as humans will last.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Wes McKinney.
Discussion
0 commentsMore from Wes McKinney
