The End of Software Engineering: What the Paper Actually Says (and Why It Walks It Back)
A paper with a provocative title landed on arXiv in June 2026. "The End of Software Engineering" sounds like war on the profession. But its argument is more measured than the title suggests.
The Core Premise
For 50 years, software engineering assumed humans encode decision logic into static code and adapt it as requirements change. The paper says AI agents break that. An agent uses an LLM as its reasoning engine, generating code as a tool and discarding it when no longer needed. Traditional software fixes decision rules before input arrives. An agent loops: pick action, execute, observe, repeat. Its core claim: the durable asset stops being code and becomes the agent that writes it.
From Software to Agent-as-a-Service
The paper traces three eras: licensed software, SaaS, and Agent-as-a-Service (AaaS). AaaS removes the software artifact as an intermediary, just as SaaS removed on-premise installation. What persists is data, permissions, business rules, and audit logs. The provocation: the world may flip from "save the program, process the data" to "save the data, generate the processing on demand."
The Evidence
The paper doesn't claim agents replace engineers today. On isolated coding tasks, they score above 80%. On sustained codebase evolution—shifting requirements, broken dependencies, accumulated context—they fall to at most 38%. Agents are real as augmentation, not yet as autonomy. It calls for "Agentic Engineering" and a roadmap toward self-evolving agent ecosystems.
The Revision
The paper's own history walks back its strongest framing. Version 1 (June 4, 2026) was titled "The End of Software Engineering: How AI Agents Are Fundamentally Restructuring the Software Paradigm." Version 2 (June 10) became "Agentic Software: How AI Agents Are Restructuring the Software Paradigm." It dropped "End" and "Fundamentally." The conclusion changed too: v1 said old software engineering is ending; v2 says it is not ending, but growing into something larger. When a paper revises its headline within a week, that matters. The useful idea survives; the doomsday framing does not.
What It Means
Software engineers aren't obsolete. The discipline's center of gravity is moving from writing decision logic by hand to specifying, orchestrating, and verifying systems that generate it. Architecture, systems thinking, and verification become more valuable, not less, because the code layer is more fluid. The durable skill is understanding what a system must do, what can go wrong, and whether it works.
The Paper
v1: https://arxiv.org/abs/2606.05608v1
v2: https://arxiv.org/abs/2606.05608v2
