“Once the product's task is known, design the interface first; then implement to the interface design.”

—  Jef Raskin , book The Humane Interface

The Humane Interface (2001)

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 "Once the product's task is known, design the interface first; then implement to the interface design." by Jef Raskin?
Jef Raskin photo
Jef Raskin 29
American computer scientist 1943–2005

Related quotes

Jef Raskin photo

“I've moved on, grown and learned in the years since then, and am designing interfaces that make the Mac's GUI feel as clumsy to use as the Mac made the old DOS-based systems feel primitive.”

Jef Raskin (1943–2005) American computer scientist

MacUser interview (2004)

Jef Raskin photo

“It would be wonderful if we could just tuck in a few loose ends and change a handful of details of present systems to have them work properly. Unfortunately, we have learned that the GUI concept has fundamental flaws that cannot be corrected by small changes. These flaws have to do with incompatibilities between the designs of both GUIs and command-line interfaces and the way our brains are wired. As we cannot change the way our minds work, we must change the interface design.”

Jef Raskin (1943–2005) American computer scientist

Sourceforge.net article "THE Is Not An Editor... So What Is It?" (2003)

Linus Torvalds photo

“The thing that has always disturbed me about O_DIRECT is that the whole interface is just stupid, and was probably designed by a deranged monkey on some serious mind-controlling substances. [*]

[*] In other words, it's an Oracleism.”

Linus Torvalds (1969) Finnish-American software engineer and hacker

Notes: from NOTES topic of open(2) manpage, 2009-04-13 http://linux.die.net/man/2/open,
2000s, 2009

“With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system.”

John Zachman (1934) American computer scientist

Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: CM Pereira (2004), "A method to define an Enterprise Architecture using the Zachman Framework". in: SAC '04 Proceedings of the 2004 ACM symposium on Applied computing. pp. 1366-1371

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.

“As more and more good ideas come under the protection of patents, it may become increasingly unlikely that any one program can incorporate the state of the art in user-interface design without sinking into a quagmire of unending royalty payments and legal battles.”

Nathaniel Borenstein (1957) American computer scientist

[Borenstein, Nathaniel S., Programming as if people mattered : friendly programs, software engineering, and other noble delusions, 1991, Princeton University Press, Princeton, N.J., 9780691087528, 52, 4. print.]
Attributed

Paul Graham photo

“Software has to be designed by hackers who understand design, not designers who know a little about software. If you can't design software as well as implement it, don't start a startup.”

Paul Graham (1964) English programmer, venture capitalist, and essayist

"The Other Road Ahead" http://www.paulgraham.com/road.html, September 2001

A. Wayne Wymore photo

“[In the year 1957] I have just returned from an exciting meeting of the American Society for Engineering Education where I heard a paper on the new discipline of systems engineering. It is no longer sufficient for engineers merely to design boxes such as computers with the expectation that they would become components of larger, more complex systems. That is wasteful because frequently the box component is a bad fit in the system and has to be redesigned or worse, can lead to system failure. We must learn how to design large-scale, complex systems from the top down so that the specification for each component is derivable from the requirements for the overall system. We must also take a much larger view of systems. We must design the man-machine interfaces and even the system-society interfaces. Systems engineers must be trained for the design of large-scale, complex, man-machine-social systems.”

A. Wayne Wymore (1927–2011) American mathematician

Systems Movement: Autobiographical Retrospectives (2004)

Marshall McLuhan photo

“There are no connections in resonant space. There are only interfaces and metamorphoses.”

Marshall McLuhan (1911–1980) Canadian educator, philosopher, and scholar-- a professor of English literature, a literary critic, and a …

Source: 1990s and beyond, The Book of Probes : Marshall McLuhan (2011), p. 75

Related topics