Tony Hoare
Tony Hoare
Sir Charles Antony Richard Hoare FRS FREng, commonly known as Tony Hoare or C. A. R. Hoare, is a British computer scientist. He developed the sorting algorithm quicksort in 1959/1960. He also developed Hoare logic for verifying program correctness, and the formal language communicating sequential processesto specify the interactions of concurrent processesand the inspiration for the occam programming language...
NationalityBritish
ProfessionScientist
Date of Birth11 January 1934
struggle simplicity program
Inside every large program is a small program struggling to get out.
simplicity reliability programming
The unavoidable price of reliability is simplicity.
mistake dollars null
I call it my billion-dollar mistake. It was the invention of the null reference in 1965.
language improvement programming
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.
determination code-quality simplicity
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.
powerful real learning
In the development of the understanding of complex phenomena, the most powerful tool available to the human intellect is abstraction. Abstraction arises from the recognition of similarities between certain objects, situations, or processes in the real world and the decision to concentrate on these similarities and to ignore, for the time being, their differences.
real skills design
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.
witty humorous simple
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.