AI-Generated Smells: An Analysis of Code and Architecture in LLM and Agent-Driven Development
Yuecai Zhu, Nikolaos Tsantalis, Peter C. Rigby
TLDR
AI-generated code, despite functional correctness, introduces significant technical debt and architectural decay, challenging current LLM development paradigms.
Key contributions
- Systematic audit reveals AI-generated software introduces distinct technical debt signatures.
- Identifies a 'Reasoning-Complexity Trade-off' leading to bloated and coupled code.
- Establishes a 'Volume-Quality Inverse Law' where code volume predicts structural degradation.
- Neither functional correctness nor detailed prompting mitigates this architectural decay.
Why it matters
This paper shifts focus from functional correctness to maintainability in AI-generated software. It highlights the need for architectural foresight in LLM agents to prevent technical debt. This reframes the central challenge of AI-based software engineering.
Original Abstract
The promise of Large Language Models in automated software engineering is often measured by functional correctness, overlooking the critical issue of long term maintainability. This paper presents a systematic audit of technical debt in AI-generated software, revealing that AI does not eliminate flaws but rather introduces a distinct machine signature of defects. Our multi-scale analysis, spanning single-file algorithmic tasks and complex, agent generated systems, identifies a fundamental Reasoning-Complexity Trade-off: as models become more capable, they generate increasingly bloated and coupled code. This architectural decay is so pronounced that we establish a Volume-Quality Inverse Law, where code volume is a near perfect predictor of structural degradation. Crucially, we demonstrate that neither functional correctness nor detailed prompting mitigates this decay. These findings challenge the current paradigm of prompt-driven generation, reframing the central problem of AI-based software engineering from one of code generation to one of architectural complexity management. We conclude that future progress depends on equipping agents with explicit architectural foresight to ensure the software they build is not just functional, but also maintainable.
📬 Weekly AI Paper Digest
Get the top 10 AI/ML arXiv papers from the week — summarized, scored, and delivered to your inbox every Monday.