1972 · Languages & software
Good software begins with reasoning about what each part must guarantee.
Visual guide
State what must be true.
Build understandable components.
Preserve the required properties.
Clear structure and explicit invariants help people reason about software before failures appear.
Testing remains valuable, but passing a collection of tests cannot establish every possible behaviour of a program.
01 · The idea
Edsger Dijkstra argued that programming is an intellectual discipline, not simply a cycle of patching failures. Structured control flow and careful reasoning make a program easier to understand as a composition of smaller parts. His contributions ranged across algorithms, concurrency and the foundations of program design.
Clear structure and explicit invariants help people reason about software before failures appear.
02 · The people
Edsger Dijkstra argued that programs should be designed so their correctness can be understood and demonstrated. His contributions ranged from shortest-path algorithms to synchronization, operating systems, and structured programming. At Eindhoven he led work on the layered THE operating system. His writing challenged programming habits that obscured reasoning and helped establish a mathematical, disciplined approach to constructing dependable software systems.
Read the biography ↗03 · Read further
Original explanations based on the official award record. The subject label is an editorial navigation aid.
Automata, grammars and algorithms helped make compilers teachable and dependable.
The story
Abstraction lets a system change inside while preserving its promises outside.
The story