The Ninety Percent Trap: Empirical Documentation on Why Generative AI Requires Deep Domain Expertise
DOI:
https://doi.org/10.14738/tecs.1405.12484Keywords:
Generative AI, software engineering, technical debt, code quality, domain expertise, empirical software engineering.Abstract
This study examines how the dominant industry narrative presents generative artificial intelligence (GenAI) as a trigger for total software automation and positive exponential outcomes. Empirical evidence from codebases and recent software-engineering studies, however, suggests a paradox: rapid generation can increase review overhead, architectural decay, and critical edge-case failures. By analysing the ArtCraft case study alongside quantitative reports from GitClear, DORA, and the empirical software-engineering literature, this paper formulates the Ninety Percent Trap: GenAI can accelerate initial scaffolding from zero to one while shifting the burden of production dependability to human experts. The paper also presents the True Cost of AI Quality (TCAQ) framework, which evaluates GenAI productivity through generation time, expert review, edge-case resolution, and technical-debt cost rather than output volume alone. An illustrative calculation shows that a two-hour generation phase can become a 112-hour end-to-end engineering effort after review, edge-case resolution, and debt mitigation. The findings indicate that domain expertise remains essential for architectural reasoning, security verification, and dependable delivery.
References
[1] M. Chen et al., "Evaluating Large Language Models Trained on Code," arXiv preprint arXiv:2107.03374, 2021.
[2] T. Zingaro et al., "The Impact of AI Code Generators on Software Engineering Education and Practice," Communications of the ACM, vol. 67, no. 3, pp. 62–71, 2024.
[3] B. Agrawal et al., "Limits of Generative Models in Complex System Design," IEEE Software, vol. 41, no. 2, pp. 48–56, 2024.
[4] F. Brooks, "No Silver Bullet—Essence and Accident in Software Engineering," IEEE Computer, vol. 20, no. 4, pp. 10–19, 1987.
[5] B. Thomas, "ArtCraft Project: Building Adobe Alternatives with LLMs and Rust," GitHub Repository & Technical Notes, 2024. [Online]. Available: https://github.com/brandonthomas/artcraft
[6] GitClear, "Coding on the Edge: AI Code Quality Report 2024—Analysis of 153M Lines of Code," GitClear Research Report, 2024.
[7] M. K. Kabir et al., "Who Answers It Better? An In-Depth Analysis of ChatGPT and Stack Overflow Answers to Software Engineering Questions," in Proc. ACM Hum.-Comput. Interact., vol. 7, no. CSCW2, 2023.
[8] DORA, "State of DevOps Report 2024: Accelerated Growth and AI Integration Chokepoints," Google Cloud / DORA Research, 2024.
[9] N. Perry et al., "Do Users Write More Insecure Code with AI Assistants?" in Proc. 2023 ACM SIGSAC Conf. on Computer and Communications Security (CCS), pp. 2785–2799, 2023.
[10] Y. LeCun, "A Path Towards Autonomous Machine Intelligence," Open Review Position Paper, 2022.
[11] S. Bubeck et al., "Sparks of Artificial General Intelligence: Early experiments with GPT-4," arXiv preprint arXiv:2303.12712, 2023.
[12] R. Jesse et al., "Large Language Models as Software Reviewers: Opportunities and Pitfalls," IEEE Software, vol. 41, no. 4, pp. 32–39, 2024.
[13] W. Cunningham, "The WyCash Portfolio Management System," ACM SIGPLAN OOPS Messenger, vol. 4, no. 2, pp. 29–30, 1992.
[14] E. Murphy-Hill et al., "What Makes a Great Software Engineer?" IEEE Transactions on Software Engineering, vol. 45, no. 9, pp. 869–887, 2019.
[15] A. S. Ross et al., "The Programmer’s Assistant: Conversational AI in Complex Software Engineering Workflows," IEEE Software, vol. 40, no. 5, pp. 50–58, 2023.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2026 Husam Altahier Amhimmid, Milad Mohammed Areir

This work is licensed under a Creative Commons Attribution 4.0 International License.