Metraipolis › archive › dc_61ae32b1ae97

Escaping the Quicksand: A Call to Arms — arXiv:2608.19674

Source
arXiv (en)
Original
https://arxiv.org/abs/2608.19674
License (as archived)
CC0-1.0
Archived
2026-10-18T11:49:51.489Z
SHA-256 of the archived text
e6b7ce57a60a89c58a176cf9d00ce91c80f5e483eaee7b4acc6a561b53539df3
Stable URL of this page
https://metraipolis.com/documento/dc_61ae32b1ae97

How to cite

Escaping the Quicksand: A Call to Arms — arXiv:2608.19674 — arXiv (en), https://arxiv.org/abs/2608.19674 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_61ae32b1ae97 (Metraipolis archive dc_61ae32b1ae97, sha256 e6b7ce57a60a89c58a176cf9d00ce91c80f5e483eaee7b4acc6a561b53539df3)
BibTeX
@misc{dc61ae32b1ae97,
  title = {Escaping the Quicksand: A Call to Arms — arXiv:2608.19674},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2608.19674},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_61ae32b1ae97; sha256 e6b7ce57a60a89c58a176cf9d00ce91c80f5e483eaee7b4acc6a561b53539df3},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.19674. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Computing has been an astonishing success - but the accumulated technical debt exposes us all to huge costs in business and societal risk. For 75 years, we've built systems to prose specifications with test-and-debug development. That works well enough for industry to thrive, but it's an expensive and ineffective feedback loop, and leaves everyone relying on shaky foundations. Now, AI-enabled engineering is amplifying the success by reducing coding costs, but also amplifies the risks, by rapidly increasing technical debt, and by automating detection of the vulnerabilities therein. How can we do better? Research has long pursued mathematical proof of correctness, which, unlike testing, can cover all cases. This too has advanced massively, but it remains hard to apply, both technically and because of a deep-seated cultural disconnect. Instead, we argue for a pragmatic approach to flexible combinations of testing, *specification*, and proof, that provides more effective feedback loops for both AI and human development. Most simply, one can incrementally co-develop executable-as-test-oracle partial specifications alongside conventional prose descriptions, code, and tests. This clarifies design and makes testing much more discriminating. Developers can and should do it today. Or, even better, one can use specifications that support the full gamut of testing, property-based testing, symbolic execution, and proof. This enables a range of intertwined feedback loops, again both for AI and humans, from cheap testing to more expensive proof. However, making it really practical needs *semantics infrastructure*: specifications and tooling for the main programming languages and other abstractions, which we now more-or-less know how to build, but which is not yet in place. We call the community to arms to create and deploy it - to enable a future built on firmer ground.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-21 in cs.SE).
Categorie arXiv: Programming Languages (cs.PL) ; Artificial Intelligence (cs.AI); Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2608.19674 — 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-10-18T11:48:10.198Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-08-21?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).