The programming language that invented modern modular code

The Software Crisis and the Limits of Early Code

In the late 1960s and early 1970s, the computing world ran headlong into what engineers called the software crisis. Hardware capabilities were advancing rapidly, allowing machines to run larger and more ambitious software systems. However, the techniques used to write programs had not kept pace. Most languages of the era allowed programmers to manipulate memory addresses and internal data structures directly from anywhere in a program. As codebases grew from hundreds of lines to tens of thousands, tracking which routine modified which global variable became nearly impossible.

When an internal data structure had to be updated to improve performance or fix a flaw, every segment of the program that directly touched that data structure could break. Small modifications caused cascading bugs throughout entire systems, making large projects fragile, expensive to maintain, and prone to catastrophic failures. Computer scientists recognized that the fundamental barrier to scaling software was not raw machine performance, but human intellectual limitations: developers could no longer reason clearly about systems whose internal parts were intimately and chaotically intertwined.

Barbara Liskov's Path to Programming Methodology

The researcher who would fundamentally alter this landscape was Barbara Liskov. After earning her bachelor's degree in mathematics from the University of California, Berkeley, in 1961, she pursued graduate studies at Stanford University. In 1968, working under artificial intelligence pioneer John McCarthy, she completed a doctoral dissertation focused on a program to play chess endgames. Her degree made her one of the earliest women in the United States to earn a doctorate in computer science.