What Happened to Dijkstra's Crisis (within the Software Crisis)?

The term 'Software Crisis' was coined at the 1968 NATO Software Engineering Conference in Garmisch, Germany, to describe the widespread difficulties in developing useful, efficient, and reliable computer programs within budget and on time. Projects were chronically late, over budget, and often failed to meet requirements, largely because the rapid advancements in hardware capabilities had outpaced the industry's ad-hoc programming practices.

Edsger W. Dijkstra, a highly influential and often controversial figure in computer science, presented his unique perspective on this crisis, which can be termed 'Dijkstra's Crisis.' While acknowledging the practical problems, Dijkstra's interpretation was more philosophical and prescriptive. He believed the core issue was a fundamental lack of intellectual discipline and mathematical rigor in programming. In his seminal 1972 Turing Award lecture, 'The Humble Programmer,' Dijkstra famously stated, 'As long as there were no machines, programming was no problem at all; when we had a few weak computers, programming became a mild problem, and now we have gigantic computers, programming has become an equally gigantic problem.'

Dijkstra advocated for a radical shift, proposing that programming should be transformed into a mathematical discipline, moving away from what he described as 'Chinese armies' of badly trained programmers towards an 'elite corps of mathematical engineers' modeled on himself. His 'Notes on Structured Programming,' circulated in 1969, became a cornerstone of his proposed solution, emphasizing program modularization, clarity, and provable correctness. This approach, along with his strong denunciation of the GOTO statement, profoundly influenced the development of structured programming.

The consequences of the broader 'Software Crisis' and Dijkstra's contributions were significant. It led to the formal establishment of 'software engineering' as a discipline, aiming to apply systematic, disciplined, and quantifiable approaches to software development. Methodologies like structured programming, object-oriented design, version control, and later agile practices emerged as efforts to manage complexity and improve software quality.

As of March 2026, the 'Software Crisis' is considered an enduring challenge, evolving with new technological landscapes. Cybersecurity threats and the demand for increasingly intricate software continue to strain development processes. A significant recent development is the discussion around a 'second software crisis,' highlighted in January 2026. This new crisis is attributed to the rapid advancement of AI coding assistants, which have dramatically increased code generation capabilities, creating a 'New Abundance Problem.' Senior engineers are reportedly 'drowning' in the volume of code requiring review and integration, as management practices struggle to adapt to this new pace. This echoes the original crisis where hardware outpaced human ability, suggesting that Dijkstra's emphasis on managing complexity and intellectual control remains highly relevant. Furthermore, in August 2025, researchers at Tsinghua University announced a breakthrough in Dijkstra's own shortest-path algorithm, shattering a long-standing time complexity barrier, demonstrating that even foundational concepts continue to be refined.