„Stojący w porcie statek jest bezpieczny, ale statków nie buduje się po to aby stały w portach.”
A ship in port is safe; but that is not what ships are built for. (ang.)
Grace Hopper:
28
Cytatów
3
Polubienia
Grace Hopper słynne cytaty
Nobody believed that I had a running compiler and nobody would touch it. They told me, computers could only do arithmetic. (ang.)
„Najlepszą rzeczą w standardach jest to, że jest z czego wybierać.”
The wonderful thing about standards is, that there are so many of them to choose from. (ang.)
„Najbardziej niebezpiecznym wyrażeniem jest „zawsze to robiliśmy w ten sposób.””
The most dangerous phrase in the language is, 'We've always done it this way. (ang.)
„Łatwiej jest po fakcie błagać o wybaczenie niż przed faktem dostać na coś pozwolenie.”
It's easier to ask forgiveness than it is to get permission. (ang.)
Źródło: Okładka http://www.chips.navy.mil/links/grace_hopper/86.gif magazynu amerykańskiej marynarki wojennej Chips Ahoy
„Życie przed II wojną światową było proste. Po wojnie zaczęliśmy tworzyć systemy.”
Life was simple before World War II. After that, we had systems. (ang.)
Źródło: Online Computer Library Center (OCLC) Newsletter, marzec/kwiecień 1987, nr 167
Grace Hopper: Cytaty po angielsku
“We must state relationships, not procedures.”
As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Kontekst: We must include in any language with which we hope to describe complex data-processing situations the capability for describing data. We must also include a mechanism for determining the priorities to be applied to the data. These priorities are not fixed and are indicated in many cases by the data.
Thus we must have a language and a structure that will take care of the data descriptions and priorities, as well as the operations we wish to perform. If we think seriously about these problems, we find that we cannot work with procedures alone, since they are sequential. We need to define the problem instead of the procedures. The Language Structures Group of the Codasyl Committee has been studying the structure of languages that can be used to describe data-processing problems. The Group started out by trying to design a language for stating procedures, but soon discovered that what was really required was a description of the data and a statement of the relationships between the data sets. The Group has since begun writing an algebra of processes, the background for a theory of data processing.
Clearly, we must break away from the sequential and not limit the computers. We must state definitions and provide for priorities and descriptions of data. We must state relationships, not procedures.
“Please cut off a nanosecond and send it over to me.”
On demonstrating a billionth of a second of electricity travel with a piece of wire, in an interview on 60 Minutes (24 August 1986)
Kontekst: In total desperation, I called over to the engineering building, and I said, "Please cut off a nanosecond and send it over to me."
As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Kontekst: We must include in any language with which we hope to describe complex data-processing situations the capability for describing data. We must also include a mechanism for determining the priorities to be applied to the data. These priorities are not fixed and are indicated in many cases by the data.
Thus we must have a language and a structure that will take care of the data descriptions and priorities, as well as the operations we wish to perform. If we think seriously about these problems, we find that we cannot work with procedures alone, since they are sequential. We need to define the problem instead of the procedures. The Language Structures Group of the Codasyl Committee has been studying the structure of languages that can be used to describe data-processing problems. The Group started out by trying to design a language for stating procedures, but soon discovered that what was really required was a description of the data and a statement of the relationships between the data sets. The Group has since begun writing an algebra of processes, the background for a theory of data processing.
Clearly, we must break away from the sequential and not limit the computers. We must state definitions and provide for priorities and descriptions of data. We must state relationships, not procedures.
Unsourced variant: The most dangerous phrase in the language is, "We've always done it this way."
The Wit and Wisdom of Grace Hopper (1987)
Grace Hopper on Late Night with David Letterman (2 October 1986) https://www.youtube.com/watch?v=1-vcErOPofQ
Kontekst: There's something you learn in your first boot-camp, or training camp: If they put you down somewhere with nothing to do, go to sleep — you don't know when you'll get any more.
As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Kontekst: We must include in any language with which we hope to describe complex data-processing situations the capability for describing data. We must also include a mechanism for determining the priorities to be applied to the data. These priorities are not fixed and are indicated in many cases by the data.
Thus we must have a language and a structure that will take care of the data descriptions and priorities, as well as the operations we wish to perform. If we think seriously about these problems, we find that we cannot work with procedures alone, since they are sequential. We need to define the problem instead of the procedures. The Language Structures Group of the Codasyl Committee has been studying the structure of languages that can be used to describe data-processing problems. The Group started out by trying to design a language for stating procedures, but soon discovered that what was really required was a description of the data and a statement of the relationships between the data sets. The Group has since begun writing an algebra of processes, the background for a theory of data processing.
Clearly, we must break away from the sequential and not limit the computers. We must state definitions and provide for priorities and descriptions of data. We must state relationships, not procedures.
The Wit and Wisdom of Grace Hopper (1987)
Kontekst: We're flooding people with information. We need to feed it through a processor. A human must turn information into intelligence or knowledge. We've tended to forget that no computer will ever ask a new question.
“You manage things, you lead people. We went overboard on management and forgot about leadership.”
The Wit and Wisdom of Grace Hopper (1987)
Kontekst: You manage things, you lead people. We went overboard on management and forgot about leadership. It might help if we ran the MBAs out of Washington.
As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Kontekst: We must include in any language with which we hope to describe complex data-processing situations the capability for describing data. We must also include a mechanism for determining the priorities to be applied to the data. These priorities are not fixed and are indicated in many cases by the data.
Thus we must have a language and a structure that will take care of the data descriptions and priorities, as well as the operations we wish to perform. If we think seriously about these problems, we find that we cannot work with procedures alone, since they are sequential. We need to define the problem instead of the procedures. The Language Structures Group of the Codasyl Committee has been studying the structure of languages that can be used to describe data-processing problems. The Group started out by trying to design a language for stating procedures, but soon discovered that what was really required was a description of the data and a statement of the relationships between the data sets. The Group has since begun writing an algebra of processes, the background for a theory of data processing.
Clearly, we must break away from the sequential and not limit the computers. We must state definitions and provide for priorities and descriptions of data. We must state relationships, not procedures.
This saying appears to be due to John Augustus Shedd; it was quoted in "Grace Hopper : The Youthful Teacher of Us All" by Henry S. Tropp in Abacus Vol. 2, Issue 1 (Fall 1984) ISSN 0724-6722 . She did repeat this saying on multiple occasions, but she called it "a motto that has stuck with me" and did not claim coinage. Additional variations and citations may be found at Quote Investigator http://quoteinvestigator.com/2013/12/09/safe-harbor/
Misattributed
“I've always been more interested in the future than in the past.”
As quoted in The Reader's Digest (October 1994), p. 185
On demonstrating a millionth of a second of electricity travel with a piece of wire, in an interview on 60 Minutes (24 August 1986)
As quoted in the U.S. Navy's Chips Ahoy magazine (July 1986) http://web.archive.org/web/20090114165606/http://www.chips.navy.mil/archives/86_jul/interview.html
David Sayre, while in a panel discussion with Hopper, as quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 277
Misattributed
“From then on, when anything went wrong with a computer, we said it had bugs in it.”
On the removal of a 2-inch-long moth from the Harvard Mark II experimental computer at Harvard in 1947, as quoted in Time (16 April 1984). Note that the term "bug" was in use by people in several technical disciplines long before that; Thomas Edison used the term, and it was common AT&T parlance in the 1920s to refer to bugs in the wires. Hopper is credited with popularizing the term's use in the computing field.
As quoted in Grace Hopper : Navy Admiral and Computer Pioneer (1989) by Charlene W. Billings, p. 74 ISBN 089490194X
As appeared in the October 1986 issue of Chips, a Department of the Navy information technology magazine
“The wonderful thing about standards is that there are so many of them to choose from.”
Attributed to Hopper, without source, in The UNIX-HATERS Handbook http://web.mit.edu/~simsong/www/ugh.pdf (1994), edited by Simson Garfinkel, Daniel Weise, and Steven Strassmann ISBN 1-56884-203-1, p. 9, this is most commonly attributed to Andrew Tanenbaum, as it appears in his book Computer Networks (1981), p. 168, but has also been attributed to Patricia Seybold and Ken Olsen.
Disputed
As spoken at Space Coast 1987 speaking about the Harvard Mark I computer. The Computer was originally She in reference to the Mark I.
“Life was simple before World War II. After that, we had systems.”
The Wit and Wisdom of Grace Hopper (1987)
On being the oldest active-duty officer in the U.S. military, in an interview on 60 Minutes (24 August 1986)
“It's easier to ask forgiveness than it is to get permission.”
As quoted in the U.S. Navy's Chips Ahoy magazine (July 1986)
As quoted in Built to Learn: The Inside Story of How Rockwell Collins Became a True Learning Organization (2003) by Cliff Purington, Chris Butler, and Sarah Fister Gale, p. 171
The future: Hardware, Software, and People in Carver https://books.google.com/books?id=5Q7uAAAAMAAJ, 1983
Actually attested since mid-19th century.
Wariant: If it's a good idea, go ahead and do it. It is much easier to apologize than it is to get permission.
Wariant: That brings me to the most important piece of advice that I can give to all of you: if you've got a good idea, and it's a contribution, I want you to go ahead and DO IT. It is much easier to apologize than it is to get permission.
Źródło: https://quoteinvestigator.com/2018/06/19/forgive/
