AI编程助手提升效率却降低可靠性，关键在规范管理而非模型能力。
The Productivity-Reliability Paradox: Specification-Driven Governance for AI-Augmented Software Development
- 提出规范治理模型，用制度约束非确定性代码生成
- 实证发现98%代码提交量增加但审查时间延长91%
- 适合关注AI开发治理的团队和架构师参考
自2022年以来，AI编程助手表现出矛盾现象：控制实验显示任务完成效率提升20%-56%，但最严谨的随机对照试验显示资深开发者效率反而下降19%；对超万名开发者的遥测数据表明，代码提交量增加98%，审查时间延长91%，交付指标基本持平。本文将此现象定义为生产力-可靠性悖论（PRP），源于非确定性代码生成与规范管理不足。通过分析67项文献（2022-2026），本文提出：(1) 明确定义PRP，包含任务抽象、代码库成熟度、开发者经验三类调节变量，以及审查瓶颈、上下文窗口限制两类放大机制；(2) 构建AI增强方法分类体系（AAMT），划分六种方法，分属三个集成层级；(3) 提出基于交易成本经济学的规范治理模型（SGM）及实用决策指南；(4) 通过四个月试点验证Spec Kit与TDAD作为SGM实例的有效性。研究表明，规范纪律才是制约AI辅助软件可靠性的关键瓶颈。
原文摘要 · Abstract (English)
Since 2022, AI-powered coding assistants have produced contradictory evidence: controlled studies report 20-56% productivity gains on well-scoped tasks, while the most rigorous RCT documents a 19% slowdown for experienced developers, and telemetry across 10,000+ developers shows 98% more pull requests but 91% longer review times with flat delivery metrics. This paper argues these findings constitute the Productivity-Reliability Paradox (PRP): a systematic phenomenon emerging from non-deterministic code generators and insufficient specification discipline. Through a multivocal literature review of 67 sources (2022-2026), this paper: (1) formally defines the PRP with three moderating variables (task abstraction, codebase maturity, developer experience) and two amplifying mechanisms (code review bottleneck, context window constraint); (2) proposes the AI-Augmented Methodology Taxonomy (AAMT), classifying six methodologies under three AI integration tiers; (3) introduces the Specification Governance Model (SGM), grounded in Transaction Cost Economics, with a practical governance decision guide; and (4) evaluates Spec Kit and TDAD as SGM instantiations via a four-month pilot study. Specification discipline, not model capability, is the binding constraint on AI-assisted software dependability.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。