Frases de Grace Hopper

Grace Murray Hopper foi uma analista de sistemas da Marinha dos Estados Unidos nas décadas de 1940 e 1950 e almirante. Foi ela quem criou a linguagem de programação Flow-Matic, hoje extinta. Esta linguagem serviu como base para a criação do COBOL. Ela também foi uma das primeiras programadoras do Harvard Mark I em 1944.

Dentre outras realizações da almirante está a criação do primeiro compilador, de COBOL, sendo a primeira linguagem de programação de computadores a se aproximar da linguagem humana ao invés da linguagem de máquina. Contudo, ela não participou efetivamente na criação da linguagem COBOL mas sim num subcomitê que foi originado de um dos três comitês propostos numa reunião no Pentágono em Maio de 1959. Este subcomitê desenvolveu as especificações da linguagem COBOL. Ele era formado por seis pessoas: William Selden e Gertrude Tierney da IBM; Howard Bromberg e Howard Discount da RCA; Vernon Reeves e Jean E. Sammet da Sylvania Electric Products.

A concepção de Hopper de que havia a necessidade de se criar uma linguagem orientada para negócios comuns deu origem ao acrônimo COBOL .

Tudo foi feito sem definir os comandos para minimizar melindres entre os técnicos das empresas convocadas a participar da criação de um denominador comum entre todos os fabricantes existentes na época. Grace Hopper participou contribuindo com a abertura dos comandos FLOW-MATIC.

É dito que é de autoria de Hopper o termo "bug" usado para designar uma falha num código-fonte.

Surgiu quando Grace tentava achar um problema no seu computador. Quando descobriu o problema, ela percebeu que havia um inseto morto no computador. Desde então o termo bug passou a ser usado.

Mas existem outras versões que contradizem a origem verdadeira do termo "bug". Uma das versões é de Thomas Edison que casualmente tem muita semelhança com a história da analista. Um inseto que causou problemas de leitura em seu fonógrafo em 1878

Em 1998, recebeu a honra de ter seu nome em um navio da Marinha. O contratorpedeiro USS Hopper entrou no serviço ativo em 1998.

✵ 9. Dezembro 1906 – 1. Janeiro 1992
Grace Hopper photo
Grace Hopper: 23   citações 0   Curtidas

Grace Hopper frases e citações

Grace Hopper: Frases em inglês

“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.

“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)
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."

“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.”

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.

“Humans are allergic to change. They love to say, "We've always done it this way." I try to fight that. That's why I have a clock on my wall that runs counter-clockwise.”

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)

“If they put you down somewhere with nothing to do, go to sleep — you don't know when you'll get any more.”

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.

“We must include in any language with which we hope to describe complex data-processing situations the capability for describing data.”

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.

“A human must turn information into intelligence or knowledge. We've tended to forget that no computer will ever ask a new question.”

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.

“You manage things, you lead people. We went overboard on management and forgot about leadership.”

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.

“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.”

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.

“A ship in port is safe; but that is not what ships are built for. Sail out to sea and do new things.”

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

“At the end of about a week, I called back and said, "I need something to compare this to. Could I please have a microsecond?"”

On demonstrating a millionth of a second of electricity travel with a piece of wire, in an interview on 60 Minutes (24 August 1986)

“At present, we're putting on paper a lot of stuff that never needed to be on paper. We do need to keep the records. But there isn't any reason for printing them. The next generation growing up with the computers will change that.”

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

“To me programming is more than an important practical art. It is also a gigantic undertaking in the foundations of knowledge.”

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.

“I had a running compiler and nobody would touch it. … they carefully told me, computers could only do arithmetic; they could not do programs.”

As quoted in Grace Hopper : Navy Admiral and Computer Pioneer (1989) by Charlene W. Billings, p. 74 ISBN 089490194X

“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

“[The Computer] was the first machine man built that assisted the power of his brain instead of the strength of his arm.”

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)

“I handed my passport to the immigration officer, and he looked at it and looked at me and said, "What are you?"”

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.
Variante: If it's a good idea, go ahead and do it. It is much easier to apologize than it is to get permission.
Variante: 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.
Fonte: https://quoteinvestigator.com/2018/06/19/forgive/

Autores parecidos

Ronald Reagan photo
Ronald Reagan 21
político estadunidense, 40° Presidente dos Estados Unidos
John Fitzgerald Kennedy photo
John Fitzgerald Kennedy 60
35º Presidente dos Estados Unidos
Martin Luther King Junior photo
Martin Luther King Junior 102
líder do movimento dos direitos civis dos negros nos Estado…
Elvis Presley photo
Elvis Presley 53
cantor dos Estados Unidos
Charles Manson photo
Charles Manson 2
fundador e líder de um grupo que cometeu vários assassinato…