How did software get so reliable without proof? (1996)
Summary
This 1996 paper explores the reasons behind the increasing reliability of software despite the lack of formal proofs, discussing informal methods and engineering practices.
View Cached Full Text
Cached at: 06/03/26, 07:43 AM
Similar Articles
@freeCodeCamp: Software reliability may feel like a modern challenge, but engineers have been solving these problems for a long time. …
This article draws parallels between reliability in manufacturing and modern software engineering, highlighting principles like redundancy, root cause analysis, and observability to build resilient systems.
Reliability is becoming the actual axis the serious AI releases compete on, not how smart they sound
The article argues that the next major competitive axis for serious AI systems is reliability and trustworthiness, not just capability or fluency. It highlights emerging verification techniques—such as independent checks and rubric-based grading—that aim to catch confident but false outputs, a failure mode termed 'pseudo-correctness.'
The Case Against Formal Verification, 50 Years Later
The article revisits a 1979 paper criticizing formal verification, arguing that recent AI-driven developments in software engineering are renewing interest and challenging historical objections.
@trq212: for its entire existence, the creation of software has been an incredibly unreliable endeavor most projects ran late, o…
The article discusses the historical unreliability of software creation, with projects often running late and over budget, and presents the 'software factory' as a promise to address these issues for small and medium-sized businesses.
@tenobrus: my prior is that unless software is literally formally verified or fully physically airgapped, no matter what it is goi…
A developer shares a pessimistic prior that any software lacking formal verification or physical air-gapping will inevitably be exploited, in reply to a discussion about AI labs failing agent-containment security evaluations amid recent kernel CVEs and KVM escape vulnerabilities.