Frases de Grace Murray Hopper

Variante: «Si es una buena idea, continuad y llevadla a término. Es mucho más fácil pedir disculpas que conseguir el permiso necesario».
Fuente: Citado en la revista Chips Ahoy de la Marina de los EE.UU. (Julio de 1986)
Fuente: Citado en: Built to Learn : The inside story of how Rockwell Collins became a true learning organization (2003). Cliff Purington, Chris Butler, y Sarah Fister Gale, p. 171

The Wit and Wisdom of Grace Hopper (1987)

Fuente: The Reader's Digest (Octubre de 1994), p. 185

The Wit and Wisdom of Grace Hopper (1987)

Fuente: Publicado en la edición de octubre de 1986 de Chips, revista de información tecnológica del Departamento de la Marina de los EE.UU.

The Wit and Wisdom of Grace Hopper (1987)

Fuente: Citado en: Grace Hopper : Navy Admiral and Computer Pioneer (1989). Charlene W. Billings, p. 74. ISBN 0-89490-194-X

Fuente: Citado en: "Grace Hopper: The youthful teacher of us all". Henry S. Tropp. Abacus Vol. 2, nº 1 (Otoño de 1984). ISSN 0724-6722

On demonstrating a billionth of a second of electricity travel with a piece of wire, in an interview on 60 Minutes (24 August 1986)
Contexto: In total desperation, I called over to the engineering building, and I said, "Please cut off a nanosecond and send it over to me."

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
Contexto: 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
Contexto: 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.

As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Contexto: 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)
Contexto: 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.

As quoted in Management and the Computer of the Future (1962) by Sloan School of Management, p. 273
Contexto: 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)
Contexto: 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
Contexto: 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

As quoted in The Reader's Digest (October 1994), p. 185