Frases de Charles Antony Richard Hoare

Charles Antony Richard Hoare, também conhecido como Tony Hoare ou C. A. R. Hoare , é um cientista da computação britânico.

Conhecido pelo desenvolvimento do Quicksort em 1960, o algoritmo de ordenação mais utilizado no mundo, e muito provavelmente o algoritmo mais usado dentre todos os tipos existentes. Ele também desenvolveu a Lógica de Hoare e a linguagem formal CSP, usada para especificar interações entre processos concorrentes e que serviu de inspiração para a linguagem de programação Occam.

Nascido em Colombo, Sri Lanka, de pais nascidos no Reino Unido, graduou-se Bacharel pela Universidade de Oxford em 1956. Ele permaneceu ainda um ano em Oxford estudando Estatística em nível de graduação, e em seguida estudou tradução computacional de linguagens humanas na Universidade de Moscou, na Rússia. Em 1960 começou a trabalhar na Elliot Brothers, Ltd, uma pequena firma de desenvolvimento de programas, onde implementou a ALGOL 60 e começou a trabalhar inicialmente desenvolvendo algoritmos. Tornou-se professor de Ciência da Computação na Queen's University, em Belfast em 1968, e em 1977 mudou-se para Oxford, também para trabalhar como professor. Hoje ocupa o cargo de Professor lá, e também é um dos pesquisadores mais antigos do centro de pesquisas da Microsoft em Cambridge, na Inglaterra.

Recebeu o Prêmio Turing da ACM de 1980, por "suas contribuições fundamentais para a definição e projeto de linguagens de programação". O prêmio lhe foi entregue na Conferência Anual da ACM em Nashville, Tennessee, em 27 de outubro de 1980, por Walter Carlson, presidente do comitê de premiação.Em 1985 foi eleito fellow da Royal Society. Em 2005 foi eleito também fellow da Royal Academy of Engineering. Wikipedia  

✵ 11. Janeiro 1934
Charles Antony Richard Hoare photo
Charles Antony Richard Hoare: 16   citações 0   Curtidas

Charles Antony Richard Hoare: Frases em inglês

“There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.”

The Emperor's Old Clothes
Contexto: There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. It demands the same skill, devotion, insight, and even inspiration as the discovery of the simple physical laws which underlie the complex phenomena of nature.

“There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way — and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.”

The Emperor's Old Clothes
Contexto: [About PL/I] At first I hoped that such a technically unsound project would collapse but I soon realized it was doomed to success. Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way — and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.

“The real value of tests is not that they detect bugs in the code, but that they detect inadequacies in the methods, concentration, and skills of those who design and produce the code.”

How Did Software Get So Reliable Without Proof? Lecture Notes in Computer Science vol 1051 1996 pp. 1-17 : FME '96: Industrial Benefit and Advances in Formal Methods, Third International Symposium of Formal Methods Europe, Co-Sponsored by IFIP WG 14.3, Oxford, UK, March 18-22, 1996, Proceedings.

“In any respectable branch of engineering, failure to observe such elementary precautions would have long been against the law”

The Emperor's Old Clothes
Contexto: [About Algol 60 subset implementation] [E]very occurrence of every subscript of every subscripted variable was on every occasion checked at run time against both the upper and the lower declared bounds of the array. Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to - they already knew how frequently subscript errors occur on production runs where failure to detect them could be disastrous. I note with fear and horror that even in 1980, language designers and users have not learned this lesson. In any respectable branch of engineering, failure to observe such elementary precautions would have long been against the law.

“[About Algol 60] Here is a language so far ahead of its time, that it was not only an improvement on its predecessors, but also on nearly all its successors.”

Hints on Programming Language Design http://i.stanford.edu/pub/cstr/reports/cs/tr/73/403/CS-TR-73-403.pdf, December 1973.

“Premature optimization is the root of all evil.”

Quote due to Donald Knuth, "Structured Programming with Goto Statements" http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf, Computing Surveys 6:4 (December 1974), pp. 261–301, §1. Knuth refers to it as "Hoare's Dictum" 15 years later in "The Errors of TeX", Software—Practice & Experience 19:7 (July 1989), pp. 607–685. However, the attribution to Hoare is doubtful. http://shreevatsa.wordpress.com/2008/05/16/premature-optimization-is-the-root-of-all-evil/
Attributed