Metraipolis › archive › dc_ada94314cd24
Disposable Implementations: What Is Software Engineering For? — arXiv:2611.04383
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2611.04383
- License (as archived)
- CC0-1.0
- Archived
- 2026-11-04T21:53:38.670Z
- SHA-256 of the archived text
a0fa95750d7bd512fcbb4d0dfb108113f858aae7b4a79df5518ead59b4dc9569- Stable URL of this page
https://metraipolis.com/documento/dc_ada94314cd24
How to cite
Disposable Implementations: What Is Software Engineering For? — arXiv:2611.04383 — arXiv (en), https://arxiv.org/abs/2611.04383 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_ada94314cd24 (Metraipolis archive dc_ada94314cd24, sha256 a0fa95750d7bd512fcbb4d0dfb108113f858aae7b4a79df5518ead59b4dc9569)
BibTeX
@misc{dcada94314cd24,
title = {Disposable Implementations: What Is Software Engineering For? — arXiv:2611.04383},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2611.04383},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_ada94314cd24; sha256 a0fa95750d7bd512fcbb4d0dfb108113f858aae7b4a79df5518ead59b4dc9569},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.04383. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Existing implementations are usually maintained for most of their life and replaced only as an exception. Coding agents may change that. If agents can produce new implementations from requirements, tests, architectural constraints, and operational records that survive replacement, changing a system may no longer require modifying its existing codebase. We call this process regeneration. An implementation is disposable when regeneration becomes a routine alternative to maintenance. Regenerating and verifying a clean implementation from current requirements and tests may be cheaper than having agents navigate (and potentially compound) existing technical debt, and could eliminate much of that debt. Yet existing code may contain knowledge absent from the preserved artifacts, including safeguards introduced after failures and assumptions that were never documented. A regenerated implementation may pass the available tests and still lose behavior that matters in production. This leaves open how to establish continuity across replacements and whether regeneration reduces maintenance effort or shifts it to the artifacts and processes that support it. We examine these questions through an exploratory review of practitioner literature. Published examples show that agents can replace existing implementations, but do not establish that repeated regeneration is safe or economical. If implementations become disposable, what should software engineering preserve? Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.SE, nuovi lavori del giorno). Categorie arXiv: Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2611.04383 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-11-04T21:39:04.517Z dalla pagina https://arxiv.org/list/cs.SE/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).