Дата рождения: 9. Декабрь 1906
Дата смерти: 1. Январь 1992
Грейс Хоппер — американская учёная и контр-адмирал флота США. Являясь первооткрывательницей в своей области, она была одной из первых, кто писал программы для гарвардского компьютера Марк I. Она разработала первый компилятор для компьютерного языка программирования, развила концепцию машинно-независимых языков программирования, что привело к созданию COBOL, одного из первых высокоуровневых языков программирования. Ей приписывается популяризация термина debugging для устранения сбоев в работе компьютера. Из-за многочисленных достижений и высокого чина во флоте её иногда называют «Удивительная Грейс», «Amazing Grace» . В её честь назван эсминец ВМФ США USS Hopper и суперкомпьютер Cray XE6 «Hopper» Исследовательского вычислительного центра министерства энергетики .
— Грейс Хоппер
С достоверным авторством, Source: Tropp, Henry S. (Fall 1984). "Grace Hopper: The Youthful Teacher of Us All". Abacus 2 (1): p. 18. ISSN 0724-6722
— Грейс Хоппер
С достоверным авторством, Source: Billings, Charlene W. (1989). Grace Hopper: Navy Admiral and Computer Pioneer, p. 74, Enslow. ISBN 089490194X
— Грейс Хоппер
Имеется в виду польза параллельных вычислений. Предпочтительнее использовать несколько обычных ПК, чем 1 дорогой суперкомпьютер. Цитата использована в качестве эпиграфа к 1-й главе книги "Hadoop. Подробное руководство" (Т. Уайт, 2012).
— Грейс Хоппер
С достоверным авторством, Source: (March/April 1987). "The Wit and Wisdom of Grace Hopper". OCLC Newsletter (167). ISSN 0163-898X.
— Грейс Хоппер
С достоверным авторством, Source: July 1986 issue http://www.chips.navy.mil/archives/86_jul/interview.html of the U.S. Navy's Chips Ahoy magazine
— Грейс Хоппер
Приписываемые, Source: возможно, упомянуто в Компьютерных сетях, 1 изд. (1981), Эндрю Таненбаума, стр. 168, без приписывания авторства)
— Grace Hopper
Context: 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
— Grace Hopper
Context: In total desperation, I called over to the engineering building, and I said, "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)
— Grace Hopper
Context: 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.
— Grace Hopper
Context: 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
— Grace Hopper
Context: 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.
— Grace Hopper
Context: 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
