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.'
We have proof automation now
The article discusses how LLMs can automate proof generation in dependently-typed languages like Lean and Rocq, making formal verification dramatically more practical by leveraging proof irrelevance and reducing the need for manual proof engineering.
On the Reliability of Computer Use Agents
A preprint analyzing why computer-use agents succeed once but fail on repeated executions, attributing unreliability to execution stochasticity, task ambiguity, and behavioral variability, and advocating repeated evaluation and stable strategies.
You Don't Know Jack About Formal Verification
An opinion piece that explores common misconceptions about formal verification and highlights its critical role in ensuring software and AI system reliability.