Frases de Edsger Dijkstra

Edsger Wybe Dijkstra foi um cientista da computação holandês conhecido por suas contribuições nas áreas de desenvolvimento de algoritmos e programas, de linguagens de programação , sistemas operacionais e processamento distribuído.

A pronúncia aproximada em português para Edsger Dijkstra é étsrrar déikstra .

Entre suas contribuições para a ciência da computação está incluído o algoritmo para o problema do caminho mínimo , o sistema operacional THE e a construção de semáforos para coordenar múltiplos processadores e programas. Outro conceito desenvolvido pelo cientista foi a auto-estabilização na área de sistemas distribuídos, uma forma alternativa de garantir a confiança de um sistema.

O cientista também foi conhecido por seus ensaios sobre programação, tendo sido o primeiro a alegar que programação é tão inerentemente difícil e complexa que os programadores precisam realizar qualquer abstração possível para gerenciar a complexidade com sucesso.

✵ 11. Maio 1930 – 6. Agosto 2002
Edsger Dijkstra photo
Edsger Dijkstra: 71   citações 0   Curtidas

Edsger Dijkstra Frases famosas

“Testes de programas podem ser uma maneira muito eficaz para demonstrar a presença de erros, mas é irremediavelmente insuficiente para mostrar a sua ausência.”

Program testing can be a very effective way to show the presence of bugs, but is hopelessly inadequate for showing their absence.
The Humble Programmer, ACM Turing Lecture 1972

“A introdução de abstrações adequadas é a nossa única ajuda mental para reduzir o apelo à enumeração, para organizar e dominar a complexidade.”

The introduction of suitable abstractions is our only mental aid to reduce the appeal to enumeration, to organize and master complexity.
Selected writings on computing: a personal perspective - página 2, Edsger Wybe Dijkstra - Springer-Verlag, 1982, ISBN 0387906525, 9780387906522 - 362 páginas

“Ciência da Computação está tão relacionada aos computadores quanto a Astronomia aos telescópios, Biologia aos microscópios, ou Química aos tubos de ensaio. A Ciência não estuda ferramentas. Ela estuda como nós as utilizamos, e o que descobrimos com elas.”

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.
Fellows, M.R., and Parberry, I., "SIGACT trying to get children excited about CS", January 1993, Computing Research News.
Atribuídas

Edsger Dijkstra: Frases em inglês

“How do we convince people that in programming simplicity and clarity —in short: what mathematicians call "elegance"”

are not a dispensable luxury, but a crucial matter that decides between success and failure?
1980s
Fonte: EWD648.

“A programmer? But was that a respectable profession? For after all, what was programming? Where was the sound body of knowledge that could support it as an intellectually respectable discipline? I remember quite vividly how I envied my hardware colleagues, who, when asked about their professional competence, could at least point out that they knew everything about vacuum tubes, amplifiers and the rest, whereas I felt that, when faced with that question, I would stand empty-handed.”

Dijkstra (1972) The Humble Programmer http://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/EWD340.html (EWD340).
1970s
Contexto: After having programmed for some three years, I had a discussion with A. van Wijngaarden, who was then my boss at the Mathematical Center in Amsterdam, a discussion for which I shall remain grateful to him as long as I live. The point was that I was supposed to study theoretical physics at the University of Leiden simultaneously, and as I found the two activities harder and harder to combine, I had to make up my mind, either to stop programming and become a real, respectable theoretical physicist, or to carry my study of physics to a formal completion only, with a minimum of effort, and to become....., yes what? A programmer? But was that a respectable profession? For after all, what was programming? Where was the sound body of knowledge that could support it as an intellectually respectable discipline? I remember quite vividly how I envied my hardware colleagues, who, when asked about their professional competence, could at least point out that they knew everything about vacuum tubes, amplifiers and the rest, whereas I felt that, when faced with that question, I would stand empty-handed. Full of misgivings I knocked on van Wijngaarden’s office door, asking him whether I could “speak to him for a moment”; when I left his office a number of hours later, I was another person. For after having listened to my problems patiently, he agreed that up till that moment there was not much of a programming discipline, but then he went on to explain quietly that automatic computers were here to stay, that we were just at the beginning and could not I be one of the persons called to make programming a respectable discipline in the years to come? This was a turning point in my life and I completed my study of physics formally as quickly as I could. One moral of the above story is, of course, that we must be very careful when we give advice to younger people; sometimes they follow it!

“As a result, the topic became – primarily in the USA – prematurely known as ‘computer science’ – which, actually, is like referring to surgery as ‘knife science’ – and it was firmly implanted in people’s minds that computing science is about machines and their peripheral equipment. Quod non”

Dijkstra (1986) On a cultural gap http://www.cs.utexas.edu/users/EWD/transcriptions/EWD09xx/EWD924.html (EWD 924).
1980s
Contexto: A confusion of even longer standing came from the fact that the unprepared included the electronic engineers that were supposed to design, build and maintain the machines. The job was actually beyond the electronic technology of the day, and, as a result, the question of how to get and keep the physical equipment more or less in working condition became in the early days the all-overriding concern. As a result, the topic became – primarily in the USA – prematurely known as ‘computer science’ – which, actually, is like referring to surgery as ‘knife science’ – and it was firmly implanted in people’s minds that computing science is about machines and their peripheral equipment. Quod non [Latin: "Which is not true"]. We now know that electronic technology has no more to contribute to computing than the physical equipment. We now know that programmable computer is no more and no less than an extremely handy device for realizing any conceivable mechanism without changing a single wire, and that the core challenge for computing science is hence a conceptual one, viz., what (abstract) mechanisms we can conceive without getting lost in the complexities of our own making.

“Program testing can be used to show the presence of bugs, but never to show their absence!”

Dijkstra (1970) " Notes On Structured Programming http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD249.PDF" (EWD249), Section 3 ("On The Reliability of Mechanisms"), corollary at the end.
1970s
Variante: Program testing can be a very effective way to show the presence of bugs, but it is hopelessly inadequate for showing their absence.

“The question of whether Machines Can Think… is about as relevant as the question of whether Submarines Can Swim.”

Dijkstra (1984) The threats to computing science http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD898.html (EWD898).
1980s

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

Dijkstra (2000), "Answers to questions from students of Software Engineering" http://www.cs.utexas.edu/~EWD/ewd13xx/EWD1305.PDF (EWD 1305).
2000s

“Thank goodness we don't have only serious problems, but ridiculous ones as well.”

Dijkstra (1982) "A Letter to My Old Friend Jonathan" (EWD475) p. 101 in [Dijkstra, Edsger, Selected Writings on Computing, Springer-Verlag, Berlin, 1982, 9780387906522]
1980s

“A convincing demonstration of correctness being impossible as long as the mechanism is regarded as a black box, our only hope lies in not regarding the mechanism as a black box.”

Dijkstra (1970) " Notes On Structured Programming http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD249.PDF" (EWD249), Section 3 ("On The Reliability of Mechanisms"), p. 5.
1970s

“Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better.”

Dijkstra (1984) On the nature of Computing Science http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD896.html (EWD896).
1980s

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

Dijkstra (EWD1239: A first exploration of effective reasoning)
1990s

“Simplicity is prerequisite for reliability.”

1970s, How do we tell truths that might hurt? (1975)

“One moral of the above story is, of course, that we must be very careful when we give advice to younger people; sometimes they follow it!”

Dijkstra (1972) The Humble Programmer http://www.cs.utexas.edu/users/EWD/transcriptions/EWD03xx/EWD340.html (EWD340).
1970s
Contexto: After having programmed for some three years, I had a discussion with A. van Wijngaarden, who was then my boss at the Mathematical Center in Amsterdam, a discussion for which I shall remain grateful to him as long as I live. The point was that I was supposed to study theoretical physics at the University of Leiden simultaneously, and as I found the two activities harder and harder to combine, I had to make up my mind, either to stop programming and become a real, respectable theoretical physicist, or to carry my study of physics to a formal completion only, with a minimum of effort, and to become....., yes what? A programmer? But was that a respectable profession? For after all, what was programming? Where was the sound body of knowledge that could support it as an intellectually respectable discipline? I remember quite vividly how I envied my hardware colleagues, who, when asked about their professional competence, could at least point out that they knew everything about vacuum tubes, amplifiers and the rest, whereas I felt that, when faced with that question, I would stand empty-handed. Full of misgivings I knocked on van Wijngaarden’s office door, asking him whether I could “speak to him for a moment”; when I left his office a number of hours later, I was another person. For after having listened to my problems patiently, he agreed that up till that moment there was not much of a programming discipline, but then he went on to explain quietly that automatic computers were here to stay, that we were just at the beginning and could not I be one of the persons called to make programming a respectable discipline in the years to come? This was a turning point in my life and I completed my study of physics formally as quickly as I could. One moral of the above story is, of course, that we must be very careful when we give advice to younger people; sometimes they follow it!

“Testing shows the presence, not the absence of bugs”

Dijkstra (1969) J.N. Buxton and B. Randell, eds, Software Engineering Techniques, April 1970, p. 16. Report on a conference sponsored by the NATO Science Committee, Rome, Italy, 27–31 October 1969. http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1969.PDF Possibly the earliest documented use of the famous quote.
1960s

Autores parecidos

Nikola Tesla photo
Nikola Tesla 13
inventor sérvio-americano
Carl Sagan photo
Carl Sagan 51
grande cientista do séc XX, criador da aclamada série Cosmo…
Erwin Schrödinger photo
Erwin Schrödinger 4
físico teórico austríaco
Max Planck photo
Max Planck 7
professor académico alemão
Marie Curie photo
Marie Curie 14
química e física polonesa naturalizada primeiro russa, e, e…
James Joyce photo
James Joyce 46
escritor irlandês do século XX, mais conhecido por escrever…
Stephen Hawking photo
Stephen Hawking 23
físico teórico