Edsger Dijkstra
Edsger Dijkstra
Edsger Wybe Dijkstra; 11 May 1930 – 6 August 2002) was a Dutch computer scientist. A theoretical physicist by training, he worked as a programmer at the Mathematisch Centrumfrom 1952 to 1962. He was a professor of mathematics at the Eindhoven University of Technologyand a research fellow at the Burroughs Corporation. He held the Schlumberger Centennial Chair in Computer Sciences at the University of Texas at Austin from 1984 until 1999, and retired as Professor Emeritus in 1999...
wise learning space
...our intellectual powers are rather geared to master static relations and that our powers to visualize processes evolving in time are relatively poorly developed. For that reason we should do (as wise programmers aware of our limitations) our utmost to shorten the conceptual gap between the static program and the dynamic process, to make the correspondence between the program (spread out in text space) and the process (spread out in time) as trivial as possible.
witty teaching humorous
The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense.
real challenges world
Beware of "the real world". A speaker's apeal to it is always an invitation not to challenge his tacit assumptions.
exploitation activity abstraction
The effective exploitation of his powers of abstraction must be regarded as one of the most vital activities of a competent programmer.
appreciate ingredients steps
The traditional mathematician recognizes and appreciates mathematical elegance when he sees it. I propose to go one step further, and to consider elegance an essential ingredient of mathematics: if it is clumsy, it is not mathematics.
tools use telescopes
Computer science is no more about computers than astronomy is about telescopes, biology is about microscopes or chemistry is about beakers and test tubes. Science is not about tools. It is about how we use them, and what we find out when we do.
people suffering fool
Several people have told me that my inability to suffer fools gladly is one of my main weaknesses.
powerful machines computer
When we had no computers, we had no programming problem either. When we had a few computers, we had a mild programming problem. Confronted with machines a million times as powerful, we are faced with a gigantic programming problem.
teaching recovery college
I think of the company advertising "Thought Processors" or the college pretending that learning BASIC suffices or at least helps, whereas the teaching of BASIC should be rated as a criminal offence: it mutilates the mind beyond recovery.
thinking naive
Probably I am very naive, but I also think I prefer to remain so, at least for the time being and perhaps for the rest of my life.
book writing numbers
In this respect a program is like a poem: you cannot write a poem without writing it. Yet people talk about programming as if it were a production process and measure "programmer productivity" in terms of "number of lines of code produced". In so doing they book that number on the wrong side of the ledger: we should always refer to "the number of lines of code spent".
maturity engineering snakes
… what society overwhelmingly asks for is snake oil. Of course, the snake oil has the most impressive names — otherwise you would be selling nothing — like “Structured Analysis and Design”, “Software Engineering”, “Maturity Models”, “Management Information Systems”, “Integrated Project Support Environments” “Object Orientation” and “Business Process Re-engineering”.
humorous disease problem
PL/1, the fatal disease, belongs more to the problem set than to the solution set.
responsibility profound influence
When we take the position that it is not only the programmer's responsibility to produce a correct program but also to demonstrate its correctness in a convincing manner, then the above remarks have a profound influence on the programmer's activity: the object he has to produce must be usefully structured.