When Code Becomes Abundant: Redefining Software Engineering Around Orchestration and Verification

TL;DR

This work argues that rapid AI-driven code generation and rising energy costs compress the Software Engineering lifecycle, threatening accountability if humans are detached from decisions about what to build and how systems are verified. It proposes redefining SE around intent articulation, architectural control, and continuous verification, with architecture acting as a governance surface and maintenance reframed as ongoing verification across regenerations. The paper introduces the concepts of Orchestration and Verification as primary human responsibilities and analyzes their implications for research, education, and industrial practice. The approach aims to preserve accountability, traceability, and safety in increasingly automated, regenerating software ecosystems, impacting how SE is taught, researched, and executed.

Abstract

Software Engineering (SE) faces simultaneous pressure from AI automation (reducing code production costs) and hardware-energy constraints (amplifying failure costs). We position that SE must redefine itself around human discernment-intent articulation, architectural control, and verification-rather than code construction. This shift introduces accountability collapse as a central risk and requires fundamental changes to research priorities, educational curricula, and industrial practices. We argue that Software Engineering, as traditionally defined around code construction and process management, is no longer sufficient. Instead, the discipline must be redefined around intent articulation, architectural control, and systematic verification. This redefinition shifts Software Engineering from a production-oriented field to one centered on human judgment under automation, with profound implications for research, practice, and education.

Figures (1)

• Figure 1: Conceptual illustration of SDLC compression under automation and physical constraints.