How Did Software Get So Reliable Without Proof?
Despite early fears that software systems would be too error-prone to scale, modern software has become remarkably reliable. This reliability emerged not from widespread formal proofs, but from sound engineering practices like rigorous project management, comprehensive testing, and defensive design.
More about Tony Hoare →
Summary
Tony Hoare argues that these practical methods mirror those in traditional engineering disciplines, helping teams systematically reduce errors and improve reliability over time. Although formal methods are rarely applied directly in large-scale software, they provide foundational concepts that inform best practices—such as structured programming, strong typing, and modular design. Hoare calls for ongoing education, improved tooling, and deeper collaboration between researchers and industry, highlighting the importance of unifying theoretical advancements with real-world application.
Quotes from How Did Software Get So Reliable Without Proof?
“In all branches of commerce and industry, history shows dramatic reduction in the error rates when their cost is brought back from the customer to the perpetrator.”
Tony Hoare (verified)
Details
• Title: How Did Software Get So Reliable Without Proof?
• Author: Tony Hoare
• Type: Article
• Journal: FME'96: Industrial Benefit and Advances in Formal Methods (Conference)
• Publisher: Springer
• Publication time: March, 1996
• Publication place: Berlin and Heidelberg, Germany
• ISBN: 978-3-540-60973-5
• Link: https://link.springer.com/chapter/10.1007/3-540-60973-3_77
People also read