Дата рождения: 9. Декабрь 1906
Дата смерти: 1. Январь 1992
Грейс Хоппер — американская учёная и коммодор флота США. Будучи первооткрывательницей в своей области, она была одной из первых, кто писал программы для гарвардского компьютера Марк I. Она разработала первый компилятор для компьютерного языка программирования, развила концепцию машинно-независимых языков программирования, что привело к созданию COBOL, одного из первых высокоуровневых языков программирования. Ей приписывается популяризация термина debugging для устранения сбоев в работе компьютера. Из-за многочисленных достижений и высокого чина во флоте её иногда называют «Удивительная Грейс», «Amazing Grace» . В её честь назван эсминец ВМФ США USS Hopper и суперкомпьютер Cray XE6 «Hopper» Исследовательского вычислительного центра министерства энергетики .
С достоверным авторством
Источник: Tropp, Henry S. (Fall 1984). "Grace Hopper: The Youthful Teacher of Us All". Abacus 2 (1): p. 18. ISSN 0724-6722
Приписываемые
Источник: возможно, упомянуто в Компьютерных сетях, 1 изд. (1981), Эндрю Таненбаума, стр. 168, без приписывания авторства)
С достоверным авторством
Источник: Billings, Charlene W. (1989). Grace Hopper: Navy Admiral and Computer Pioneer, p. 74, Enslow. ISBN 089490194X
Имеется в виду польза параллельных вычислений. Предпочтительнее использовать несколько обычных ПК, чем 1 дорогой суперкомпьютер. Цитата использована в качестве эпиграфа к 1-й главе книги "Hadoop. Подробное руководство" (Т. Уайт, 2012).
С достоверным авторством
Источник: (March/April 1987). "The Wit and Wisdom of Grace Hopper". OCLC Newsletter (167). ISSN 0163-898X.
С достоверным авторством
Источник: July 1986 issue http://www.chips.navy.mil/archives/86_jul/interview.html of the U.S. Navy's Chips Ahoy magazine
Grace Hopper on Late Night with David Letterman (2 October 1986) https://www.youtube.com/watch?v=1-vcErOPofQ
Контексте: 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
Контексте: 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
Контексте: 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
Контексте: 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.
On demonstrating a billionth of a second of electricity travel with a piece of wire, in an interview on 60 Minutes (24 August 1986)
Контексте: In total desperation, I called over to the engineering building, and I said, "Please cut off a nanosecond and send it over to me."
Контексте: 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
Контексте: 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.
Контексте: 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 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.
Вариант: If it's a good idea, go ahead and do it. It is much easier to apologize than it is to get permission.
Вариант: 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.
Источник: https://quoteinvestigator.com/2018/06/19/forgive/
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
