“System designers who do not allow users to type far ahead ought to be tarred and feathered, or worse yet, be forced to use their own system.”

—  Andrew S. Tanenbaum

Operating Systems Design and Implementation, 3rd ed., p. 310.

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "System designers who do not allow users to type far ahead ought to be tarred and feathered, or worse yet, be forced to …" by Andrew S. Tanenbaum?
Andrew S. Tanenbaum photo
Andrew S. Tanenbaum 22
Dutch computer scientist 1944

Related quotes

Béla H. Bánáthy photo

“When it comes to the design of social and societal systems of all kinds, it is the users, the people in the system who are the experts. Nobody has the right to design social systems for someone else. It is unethical to do so. Design cannot be legislated, it should not be bought from the expert, and it should not be copied from the design of others. If the privilege of and responsibility for design is "given away," others will take charge of designing our lives and our systems. They will shape our future.”

Béla H. Bánáthy (1919–2003) Hungarian linguist and systems scientist

Source: Designing Social Systems in a Changing World (1996), p. 128; Cited in: Roberto Joseph et al. (2002) " Banathy's Influence on the Guidance System for Transforming Education http://www.indiana.edu/~syschang/decatur/reigeluth_pubs/documents/95_banathy_influence_on_gste.pdf". World Futures: The Journal of General Evolution, 58(5/6) 379-394

Ed Yourdon photo

“Designed as a companion volume to the acclaimed Object-Oriented Analysis, this book focuses on the middle part of the software lifecycle: the activity of design. It shows readers how to apply object-oriented design, and how to tailor and expand the method to suit specific organization and project needs. Readers will explore the major issues in OOD; the role of OOD in the systems lifecycle; how to use graphical notation; strategies for creating design; and hints for evaluating the efficiency of a design created with OOD. For software engineers and other users undertaking real-world systems development projects and designing overall software architecture for systems will find this reference approach to improving systems design indispensable.”

Ed Yourdon (1944–2016) American software engineer and pioneer in the software engineering methodology

Abstract.
Object-oriented design (1991)

Gerrit Blaauw photo

“The architecture of a system can be defined as the functional appearance of the system to the user.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Blaauw (1972) cited in: Gerritt A Blaauw (1976) Digital system implementation. p. 6

Tony Buzan photo

“During the renaissances in thinking led by Shakespeare and Goethe, the first new development in memory techniques for 1,700 years appeared: the Major System. This was the first system that enabled the user to transfer easily and instantaneously from numbers to letters, thus creating the opportunity for a system that could stretch from zero to an infinite number, and which allowed the user to translate any word into its own special number, and any number into its own special letter. This multiplied the opportunity for developing memory techniques 100-fold.”

Tony Buzan (1942–2019) British psychologist

The Mind Map Book, Buzan and Buzan (1991)

A. Wayne Wymore photo

“In the minds of many writers systems engineering is synonomous with component selection and interface design; that is, the systems engineer does not design hardware but decides what types of existing hardware shall be coupled and how they shall be coupled. Complete agreement that this function is the essence of systems engineering will not be found here, for, besides the very important function of systems engineering in systems analysis, there is the role played by systems engineering in providing boundary conditions for hardware design.”

A. Wayne Wymore (1927–2011) American mathematician

Source: A Mathematical Theory of Systems Engineering (1967), p. 193.

Gerrit Blaauw photo

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the first of them, the following working definition is given: The architecture of a system can be defined as the functional appearance of the system to the user, its phenomenology.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Although the term architecture was introduced only ten years ago in computer technology (Buchholz), the concept of architecture is as old as the use of mechanism by man. When a child is taught to look at a clock, it is taught the architecture of the clock. It is told to observe the position of the short and the long hand and to relate these to the hours and the minutes. Once it can distinguish the architecture from the visual appearance, it can tell time as easily from a wrist watch as from the clock on the church tower.
The inner structure of a system is not considered by the architecture: we do not need to know what makes the clock tick, to know what time it is. This inner structure, considered from a logical point of view, will be called the implementation, and its physical embodiment the realisation.
Source: Computer architecture (1972), p. 154

Ivar Jacobson photo

“When a user uses the system, she or he will perform a behaviorally related sequence of transactions in a dialogue with the system. We call such a special sequence a use case.”

Ivar Jacobson (1939) Swedish computer scientist

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 127; as cited in: Journal of Object-oriented Programming Vol 10, Nr 2-9. p. 32.

Ivar Jacobson photo

“A use case is a complete course of events in the system, seen from a user’s perspective.”

Ivar Jacobson (1939) Swedish computer scientist

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 157.

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

Gilad Bracha photo

“The wonderful thing about dynamic typing is it lets you express anything that is computable. And type systems don’t — type systems are typically decidable, and they restrict you to a subset. People who favor static type systems say “it’s fine, it’s good enough; all the interesting programs you want to write will work as types”. But that’s ridiculous — once you have a type system, you don’t even know what interesting programs are there.”

Gilad Bracha American software engineer

Software Engineering Radio Episode 140: Newspeak and Pluggable Types with Gilad Bracha http://www.se-radio.net/2009/07/episode-140-newspeak-and-pluggable-types-with-gilad-bracha/

Related topics