Why software remains a persistent crisis despite decades of hardware perfection
In short: In 1948, the first modern computer arrived in Manchester. Since then, software has faced three distinct crises. While hardware has become superbly engineered and ultrareliable, our software systems often remain neither, leaving us vulnerable to even the most amateur hackers.
The history of computing is marked by a recurring struggle to manage software complexity. Following the emergence of the first modern computer in Manchester in 1948, the industry moved rapidly from early business software toward a major 'Software Crisis' by 1968. This prompted a NATO conference to diagnose the issue, yet the proposed solutions were largely ignored. A second software crisis emerged in the early 1980s, characterized by a stalemate where effective solutions were deemed impractical, while practical ones proved ineffective. This cycle of failure has repeated for decades. Experts have repeatedly failed to implement lasting fixes for these recurring issues.
As Moore's Law drove hardware costs down exponentially, software became ubiquitous, eventually triggering a third crisis: one of cybersecurity. This vulnerability is exacerbated by the sheer scale of modern code. Research indicates that software typically enters service with more than ten defects for every thousand lines of program source code (KLoC). For systems containing millions of lines of code, this implies the existence of thousands of defects. The sheer volume of code creates massive risks. Such immense complexity makes it impossible to eliminate every single error.
A fundamental challenge in managing these errors is the limitation of testing. Testing is designed to find the most obvious errors; consequently, increased testing tends to uncover only the most obscure remaining bugs. This explains why software can appear to work well enough most of the time, yet remains insecure against even teenage hackers. While hardware has reached a state of high reliability, the software layer remains a persistent point of failure in our digital infrastructure. This creates a dangerous disparity in engineering standards. We rely on systems that lack the robustness of their physical components.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: A Very Brief History of Computing, 1948-2015 - Professor Martyn Thomas CBE
- Also: A Very Brief History of Computing, 1948-2015
To cite this card, link to https://intellectplus.co.uk/app/ideas-a-very-brief-history-of-computing-1948-2015-professor-martyn.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
