All Quotes

"I mean, if 10 years from now, when you are doing something quick and dirty, you suddenly visualize that I am looking over your shoulders and say to yourself "Dijkstra would not have liked this", well, that would be enough immortality for me."

"A picture may be worth a thousand words, a formula is worth a thousand pictures."

"It is time to unmask the computing community as a Secret Society for the Creation and Preservation of Artificial Complexity."

"Elegance is not a dispensable luxury but a quality that decides between success and failure."

"Industry suffers from the managerial dogma that for the sake of stability and continuity, the company should be independent of the competence of individual employees. Hence industry rejects any methodological proposal that can be viewed as making intellectual demands on its work force. Since in the US the influence of industry is more pervasive than elsewhere, the above dogma hurts American computing science most. The moral of this sad part of the story is that as long as computing science is not allowed to save the computer industry, we had better see to it that the computer industry does not kill computing science."

"May, in spite of all distractions generated by technology, all of you succeed in turning information into knowledge, knowledge into understanding, and understanding into wisdom."

"The required techniques of effective reasoning are pretty formal, but as long as programming is done by people that don't master them, the software crisis will remain with us and will be considered an incurable disease. And you know what incurable diseases do: they invite the quacks and charlatans in, who in this case take the form of Software Engineering gurus."

"It is not the task of the University to offer what society asks for, but to give what society needs."

"There are very different programming styles. I tend to see them as Mozart versus Beethoven. When Mozart started to write, the composition was finished. He wrote the manuscript and it was 'aus einem Guss' (from one cast). In beautiful handwriting, too. Beethoven was a doubter and a struggler who started writing before he finished the composition and then glued corrections onto the page. In one place he did this nine times. When they peeled them, the last version proved identical to the first one."

"What is the shortest way to travel from Rotterdam to Groningen, in general: from given city to given city. It is the algorithm for the shortest path, which I designed in about twenty minutes. One morning I was shopping in Amsterdam with my young fiancée, and tired, we sat down on the café terrace to drink a cup of coffee and I was just thinking about whether I could do this, and I then designed the algorithm for the shortest path. As I said, it was a twenty-minute invention. In fact, it was published in '59, three years late. The publication is still readable, it is, in fact, quite nice. One of the reasons that it is so nice was that I designed it without pencil and paper. I learned later that one of the advantages of designing without pencil and paper is that you are almost forced to avoid all avoidable complexities. Eventually that algorithm became, to my great amazement, one of the cornerstones of my fame."

"In short, I suggest that the programmer should continue to understand what he is doing, that his growing product remains firmly within his intellectual grip. It is my sad experience that this suggestion is repulsive to the average experienced programmer, who clearly derives a major part of his professional excitement from not quite understanding what he is doing. In this streamlined age, one of our most undernourished psychological needs is the craving for Black Magic and apparently the automatic computer can satisfy this need for the professional software engineer, who is secretly enthralled by the gigantic risks he takes in his daring irresponsibility. For his frustrations I have no remedy......"

"This is generally true: any sizeable piece of program, or even a complete program package, is only a useful tool that can be used in a reliable fashion, provided that the documentation pertinent for the user is much shorter than the program text. If any machine or system requires a very thick manual, its usefulness becomes for that very circumstance subject to doubt!"

"The precious gift that this Turing Award acknowledges is Dijkstra's style: his approach to programming as a high, intellectual challenge; his eloquent insistence and practical demonstration that programs should be composed correct, not just debugged into correctness; and his illuminating perception of problems at the foundations of program design."

"A revolution is taking place in the way we write programs and teach programming, because we are beginning to understand the associated mental processes more deeply. It is impossible to read the recent [E. W. Dijkstra, O.-J. Dahl, and C. A. R. Hoare] book Structured Programming, without having it change your life. The reason for this revolution and its future prospects have been aptly described by E.W. Dijkstra in his 1972 Turing Award Lecture, The Humble Programmer."

"The working vocabulary of programmers everywhere is studded with words originated or forcefully promulgated by E. W. Dijkstra—display, deadly embrace, semaphore, go-to-less programming, structured programming. But his influence on programming is more pervasive than any glossary can possibly indicate."

"Edsger W. Dijkstra's 1969 "Structured Programming" article precipitated a decade of intense focus on programming techniques that has fundamentally altered human expectations and achievements in software development. Before this decade of intense focus, programming was regarded as a private, puzzle-solving activity of writing computer instructions to work as a program. After this decade, programming could be regarded as a public, mathematics-based activity of restructuring specifications into programs. Before, the challenge was in getting programs to run at all, and then in getting them further debugged to do the right things. After, programs could be expected to both run and do the right things with little or no debugging. Before, it was common wisdom that no sizable program could be error-free. After, many sizable programs have run a year or more with no errors detected. These expectations and achievements are not universal because of the inertia of industrial practices. But they are well-enough established to herald fundamental change in software development."

"The difference between a computer programmer and a computer scientist is a job-title thing. Edsgar Dijkstra wants proudly to be called a "computer programmer," although he hasn't touched a computer now for some years. (...) His great strength is that he is uncompromising. It would make him physically ill to think of programming in C++."

"You probably know that arrogance, in computer science, is measured in nanodijkstras."

"...I also discovered books of two great computer scientists from whose work I learned the scientific foundation of my trade: Donald Knuth and Edsger Dijkstra. Knuth taught me the answers. Dijkstra taught me the questions. Time and time again I come back to their works for new insights."

"The first classic is one of the great works in computer programming: E. W. Dijkstra, Cooperating Sequential Processes (1965). Here Dijkstra lays the conceptual foundation for abstract concurrent programming."

"The Edsger W. Dijkstra Prize in Distributed Computing is named for Edsger Wybe Dijkstra (1930-2002), a pioneer in the area of distributed computing. His foundational work on concurrency primitives (such as the semaphore), concurrency problems (such as mutual exclusion and deadlock), reasoning about concurrent systems, and self-stabilization comprises one of the most important supports upon which the field of distributed computing is built. No other individual has had a larger influence on research in principles of distributed computing. The prize is given for outstanding papers on the principles of distributed computing, whose significance and impact on the theory and/or practice of distributed computing have been evident for at least a decade."

"Most experienced IT professionals will agree that developing and adhering to a standard architecture is key to the success of large-scale software development. Computer pioneer Edsger Dijkstra validated this notion when he developed THE operating system in 1968. Since then, layered architectures have proved their viability in technological domains, such as hardware and networking. Layering has proved itself in the operating system domain; however, the same benefits are available when applied to e-commerce or to thin client–oriented applications. Layered architectures have become essential in supporting the iterative development process by promoting reusability, scalability, and maintainability."

"Edsger Dijkstra, one of the giants of our field and a passionate believer in the mathematical view of programs and programming (...) Over the previous quarter-century, he had formulated many of the great intellectual challenges of the field as programming—the goto statement, structured programming, concurrent processes, semaphores, deadlocks, recursive programming in Algol, and deriving correct programs."

"Of great influence to Pascal was Structured Programming, put forth by E. W. Dijkstra. This method of proceeding in a design would obliviously be greatly encouraged by the use of a Structured Language, a language with a set of constructs that could freely be combined and nested. The textual structure of a program should directly reflect its flow of control."

"In 1965 Dijkstra wrote his famous Notes on Structured Programming and declared programming as a discipline in contrast to a craft. Also in 1965 Hoare published an important paper about data structuring. These ideas had a profound influence on new programming language, in particular Pascal. Languages are the vehicles in which these ideas were to be expressed. Structured programming became supported by a structured programming language."

"The notion of the concurrent program as a means for writing parallel programs without regard for the underlying hardware was first introduced by Edsger Dijkstra (1968). Moti Ben-Ari (1982) elegantly summed up Dijkstra's idea in three sentences: 'Concurrent programming is the name given to programming notation and techniques for expressing potential parallelism and solving the resulting synchronization and communication problems. Implementation of parallelism is a topic in computer systems (hardware and software) that is essentially independent of concurrent programming. Concurrent programming is important because it provides an abstract setting in which to study parallelism without getting bogged down in the implementation details.'"

"The revolution in views of programming started by Dijkstra's iconoclasm led to a movement known as structured programming, which advocated a systematic, rational approach to program construction. Structured programming is the basis for all that has been done since in programming methodology, including object-oriented programming. As the first book on the topic [Structured Programming by Dijkstra, Ole-Johan Dahl, and Tony Hoare] shows, structured programming is about much more than control structures and the goto. Its principal message is that programming should be considered a scientific discipline based on mathematical rigor."

"Since the early work of E.W. Dijkstra (1965), who introduced the mutual exclusion problem, the concept of a process, the semaphore object, the notion of a weakest precondition, and guarded commands (among many other contributions), synchronization is no longer a catalog of tricks but a domain of computing science with its own concepts, mechanisms, and techniques whose results can be applied in many domains. This means that process synchronization has to be a major topic of any computer science curriculum."

"Although Dijkstra will always be remembered for structured programming, and for his style and approach, he also invented many other of the standard ideas of programming. If you are struggling with multi-threaded programming you may have encountered the semaphore, and the idea of the "deadly embrace". These, and more, are the result of Dijkstra's work on concurrent programming. He showed how this particularly difficult area of programming could be made relatively safe."

"While concurrent program execution had been considered for years, the computer science of concurrency began with Edsger Dijkstra's seminal 1965 paper that introduced the mutual exclusion problem. (...) The first scientific examination of fault tolerance was Dijkstra's seminal 1974 paper on self-stabilization. (...) The ensuing decades have seen a huge growth of interest in concurrency—particularly in distributed systems. Looking back at the origins of the field, what stands out is the fundamental role played by Edsger Dijkstra, to whom this history is dedicated."

"Surrealism will at least have served to give experimental proof that total sterility and attempts at automatizations have gone too far and have led to a totalitarian system.. .Today's laziness and the total lack of technique have reached their paroxysm in the psychological signification of the current use of the college [= collage]."

"We generally trace the idea of building computer systems in layers back to a 1967 paper that the Dutch computer scientist Edsger Dijkstra gave to a joint IEEE Computer Society/ACM conference. Prior to this paper, engineers had struggled with the problem of how to organize software. If you look at early examples of programs, and you can find many in the electronic library of the Computer Society, you will find that most code of that era is complicated, difficult to read, hard to modify, and challenging to reuse. In his 1967 paper, Dijkstra described how software could be constructed in layers and gave an example of a simple operating system that used five layers. He admitted that this system might not be a realistic test of his ideas but he argued that the "larger the project, the more essential the structuring!" The idea of using layers to control complexity has become a mainstay of software architecture. We see it in many forms and apply it to many problems. We see it in the hierarchy of classes in object-oriented programming and in the structure of Service-Oriented Architecture (SOA). SOA is a relatively recent application of layering in computer science. It was articulated in 2007 as a means of controlling complexity in business systems, especially distributed systems that make substantial use of the Internet. Like Dijkstra's plan for system development, its layering system is called the SOA Solution Stack or S3. The S3's nine layers are: 1) operational systems, 2) service components, 3) services, 4) business processes, 5) consumer actions, 6) system integration, 7) quality control and assurance, 8) information architecture, and 9) system governance and policies."

"Computer Science is no more about computers than astronomy is about telescopes."

"Go To statement considered harmful"

"Telephone, pedal washbasin, white refrigerators gleaming with Ripolin [French paint], bidet, small phonograph.. ..objects of authentic and pure poetry (MPC p. 11).. ..The Parthenon was not built as a ruin. It was built on a new surface without patina, like our automobiles. / we will not always bear on our shoulders the weight of our father's corpse."

"Just now I'm painting a beautiful woman, smiling, burnt to a crisp, with feathers of all colors, held up by a small die of burning marble; the die is in turn held up by a little puff of smoke, churned and quite; in the sky there are asses with parrot-heads, grasses and beach sand, all about to explode, all clean, incredible objective.."

"The more I looked at his face [of Saint Sebastian] the more curious it seemed. That said, I seemed to have always known it and the aseptic morning light revealed its smallest details which such clarity, such purity, that I was impossible moved.. .In the upper part of the heliometer was St. Sebastian's magnifying glass.. .I put my eye to the magnifying glass, product of a slow distillation, at once numerical and intuitive. Each drop of water a number. Each drop of blood a geometry."

"One morning with Ripolin [French paint] I painted a new-born that I then left to dry on the tennis-court. After two days I found it bristling with ants that made it move to the anesthetized, silent rhythm of sea-urchins. However I at once realized that this newborn child was none other than the pink breast of my girlfriend, being frenetically eaten by the shining, metallic thickness of the phonograph. But it wasn't her breast either: it was little pieces of my cigarette paper nervously grouped around the magnetic topaz of my fiancees ring."

"So, André Breton, if tonight I dream I am screwing you, tomorrow morning I will paint all of our best fucking positions with the greatest wealth of detail."

"One might think that through ecstasy we would have access to a world as far from reality as that of the dream. – The repugnant can become desirable, affection cruelty, the ugly beautiful, faults qualities, qualities black miseries."

"The Italian metaphysical movement [initiated by De Chirico ] started from the spiritual reality, a consequence of the physical miracle and it aspects grouped on an immaterial plane; all this formed a new spectral reality, in order to attain maximal, almost erotic creativity in touch. The Cubists, on the other hand, starting from this sensual-idealistic touch, found a pure, new form of spirituality. Lorca is one of those who have reached this new form of miracle by following the paths of the greatest incredulity. He does not even believe in his own hands, unless it be to turn one-legged physiological and abstract tables."

"Le prisonnier n’était plus attaché au lit que par une jambe.'Avant que les sept hommes eussent eu le temps de se reconnaître et de s’élancer, lui s’était penché sous la cheminée, avait étendu la main vers le réchaud, puis s’était redressé, et maintenant Thénardier, la Thénardier et les bandits, refoulés par le saisissement au fond du bouge, le regardaient avec stupeur élevant au-dessus de sa tête le ciseau rouge d’où tombait une lueur sinistre, presque libre et dans une attitude formidable."

"Vous êtes des malheureux, mais ma vie ne vaut pas la peine d’être tant défendue. Quant à vous imaginer que vous me feriez parler, que vous me feriez écrire ce que je ne veux pas écrire, que vous me feriez dire ce que je ne veux pas dire…'Il releva la manche de son bras gauche et ajouta:'— Tenez.'En même temps il tendit son bras et posa sur la chair nue le ciseau ardent qu’il tenait dans sa main droite par le manche de bois.'On entendit le frémissement de la chair brûlée, l’odeur propre aux chambres de torture se répandit dans le taudis. Marius chancela éperdu d’horreur, les brigands eux-mêmes eurent un frisson, le visage de l’étrange vieillard se contracta à peine, et, tandis que le fer rouge s’enfonçait dans la plaie fumante, impassible et presque auguste, il attachait sur Thénardier son beau regard sans haine où la souffrance s’évanouissait dans une majesté sereine."

"La logique ignore l’à peu près; absolument comme le soleil ignore la chandelle."

"Prospérité sociale, cela veut dire l’homme heureux, le citoyen libre, la nation grande."

"La pensée est le labeur de l’intelligence, la rêverie en est la volupté."

"Heureux, même dans les angoisses, celui à qui Dieu a donné une âme digne de l’amour et du malheur! Qui n’a pas vu les choses de ce monde et le cœur des hommes à cette double lumière n’a rien vu de vrai et ne sait rien."

"Non, répondit-elle, je suis le diable, mais ça m’est égal."

"En 93, un chaudronnier avait acheté la maison pour la démolir, mais n’ayant pu en payer le prix, la nation le mit en faillite. De sorte que ce fut la maison qui démolit le chaudronnier."

"Où finit le télescope, le microscope commence. Lequel des deux a la vue la plus grande?"