What Happened to Dijkstra's Crisis: The End of Algol and Beginning of Software Engineering?

The mid-to-late 1960s witnessed a growing 'software crisis,' characterized by software projects that routinely ran over budget, missed deadlines, and delivered unreliable or incomplete systems. This crisis stemmed from the inability of existing ad-hoc programming methods to cope with the increasing complexity and scale of software required for new, powerful hardware. The term 'software engineering' itself was coined at the 1968 NATO Software Engineering Conference in Garmisch, Germany, convened to address these mounting challenges and propose a more disciplined, engineering-like approach to software development.

Edsger W. Dijkstra, a prominent Dutch computer scientist, became a leading voice in this movement. His seminal 1968 letter, 'Go To Statement Considered Harmful,' published in the Communications of the ACM, was a powerful critique of the unrestricted use of the `goto` statement, arguing that it led to 'spaghetti code' that was difficult to read, debug, and maintain. Dijkstra advocated for 'structured programming,' a paradigm that emphasized clear, modular code structures using constructs like sequences, selections (if-then-else), and iterations (loops) to control program flow logically. This approach aimed to make code more provable, understandable, and maintainable.

Algol, particularly Algol 60, played a complex role in this crisis and its resolution. Algol 60 was a pioneering language, introducing block structures, nested functions, and lexical scope, which were key advances towards structured programming. It became a standard for publishing algorithms in scientific articles. However, its successor, Algol 68, was criticized for its extreme complexity and an 'inappropriate documentation' that made it difficult to implement and understand, contributing to its eventual decline in widespread use. Dijkstra himself was critical of Algol 68, seeing it as a move away from the clarity he championed.

The consequences of Dijkstra's crisis were profound. Structured programming became the dominant paradigm, influencing the design of subsequent languages like Pascal, C, and Ada. The focus shifted from merely writing code to designing and managing software projects with engineering discipline. While the 'software crisis' itself is a historical term, its underlying challenges of complexity, budget overruns, and quality issues persist in modern contexts, leading some to argue that aspects of the crisis remain a 'software normality' in 2025. However, the principles championed by Dijkstra—readability, maintainability, and logical structure—remain fundamental to contemporary software development, even in languages like Go that retain a `goto` statement for specific, discouraged uses. Historians like Thomas Haigh have also offered nuanced perspectives, suggesting that the narrative of the 'software crisis' and the birth of software engineering was partly constructed by academics to promote a more mathematical vision of programming.