analiza aiqbench
This paper argues that despite the rise of AI coding agents, software engineering remains indispensable because LLMs' probabilistic nature creates a structural vacuum requiring human methodologists to ensure software trustworthiness. It posits that engineers must act as custodians who reify critical knowledge levers—methodological, domain, design, and process choices—into persistent artifacts to counteract AI limitations like semantic statelessness. The work directly addresses the evolving role of professionals in an AI-assisted development landscape, making it central to discussions on AI's impact on software creation.
Why Software Engineering Is Indispensable in the Age of Coding Agents
arXiv:2610.10226v1 Announce Type: cross Abstract: Can AI make Software Engineering (SE) -- the discipline -- obsolete? And can it make software engineers -- the professionals -- redundant? This paper argues that the rise of capable AI coding agents makes SE and software engineers essential, not obsolete: the missing foundation without which AI-assisted development produces misleadingly plausible, unverifiable, and ultimately untrustworthy software. Three structural properties of large language models (probabilistic generation, agnosticism, and semantic statelessness) create a structural vacuum that no amount of training can eliminate. Filling it requires four knowledge levers: methodological knowledge, domain knowledge, design choices, and process choices. All four must be reified as persistent artifacts, and each requires the software engineer as methodologist, mediator, and custodian.
Abstract:Can AI make Software Engineering (SE) -- the discipline -- obsolete? And can it make software engineers -- the professionals -- redundant? This paper argues that the rise of capable AI coding agents makes SE and software engineers essential, not obsolete: the missing foundation without which AI-assisted development produces misleadingly plausible, unverifiable, and ultimately untrustworthy software. Three structural properties of large language models (probabilistic generation, agnosticism, and semantic statelessness) create a structural vacuum that no amount of training can eliminate. Filling it requires four knowledge levers: methodological knowledge, domain knowledge, design choices, and process choices. All four must be reified as persistent artifacts, and each requires the software engineer as methodologist, mediator, and custodian.
Accepted for publication in Communications of the ACM. 5 pages
Software Engineering (cs.SE); Artificial Intelligence (cs.AI)
arXiv:2610.10226 [cs.SE]
(or arXiv:2610.10226v1 [cs.SE] for this version)
https://doi.org/10.48550/arXiv.2610.10226 Focus to learn more arXiv-issued DOI via DataCite (pending registration)
arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.
Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.
Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.
Text integral sub licența deschisă a publicației · 221 cuvinte
Subiecte conexe
[AINews] High Taste Testers Ep. 1
Latent Space · 17 oct. 2026

Presentation: The Five Stages of AI Maturity in Engineering Organizations - Where and Why Teams Get Stuck
InfoQ · 4 aug. 2026

Top 10 AI Engineering Tools Everyone is Using in 2026
Analytics Vidhya · 10 iun. 2026

Bring Claude Code On‑Prem with AMD Instinct GPUs
AMD · 17 aug. 2026