“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

"The Other Road Ahead" http://www.paulgraham.com/road.html, September 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 "Software has to be designed by hackers who understand design, not designers who know a little about software. If you ca…" by Paul Graham?

Paul Graham 43

English programmer, venture capitalist, and essayist 1964

Related quotes

“A little retrospection shows that although many fine, useful software systems have been designed by committees and built as part of multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.”

Fred Brooks No Silver Bullet

Page 202.
No Silver Bullet (1986)

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

“Almost 2000 years ago, the Roman architect Vitruvius recorded what makes a design good: durability (firmitas), utility (utilitas), and charm (venustas). These quality requirements still hold, for buildings as well as software systems. A well-designed system is easy to implement, is understandable and reliable, and allows for smooth evolution. Badly-designed systems may work at first, but they are hard to maintain, difficult to test, and unreliable.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 279

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

“The essence of a software entity is a construct of interlocking concepts: [… ] I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation.”

Fred Brooks No Silver Bullet

Page 182 (italics in source).
No Silver Bullet (1986)

“Systems with unknown behavioral properties require the implementation of iterations which are intrinsic to the design process but which are normally hidden from view. Certainly when a solution to a well-understood problem is synthesized, weak designs are mentally rejected by a competent designer in a matter of moments. On larger or more complicated efforts, alternative designs must be explicitly and iteratively implemented. The designers perhaps out of vanity, often are at pains to hide the many versions which were abandoned and if absolute failure occurs, of course one hears nothing. Thus the topic of design iteration is rarely discussed. Perhaps we should not be surprised to see this phenomenon with software, for it is a rare author indeed who publicizes the amount of editing or the number of drafts he took to produce a manuscript.”

Fernando J. Corbató (1926–2019) American computer scientist

"A Managerial View of the Multics System Development" http://www.multicians.org/managerial.html, Conference on Research Directions in Software Technology, Providence, Rhode Island, October 10-12, 1977 published in Research Directions in Software Technology (1978), P. Wegner (ed.), MIT Press, ISBN 0262230968, pp. 139-158. Also reprinted in Tutorial: Software Management, Donald J. Reifer (ed.), IEEE Computer Society Press, (1979, 1981, 1986)

“Encapsulation is the key to increasing the value of such software metrics as reusability, refinability, testability, maintainability, and extensibility. Object-oriented languages provide a number of mechanisms for improving encapsulation, but it is during the design phase that the greatest leverage can be realized.
The data-driven approach to object-oriented design focuses on the structure of the data in a system. This results in the incorporation of structural information in the definitions of classes. Doing so violates encapsulation.
The responsibility-driven approach emphasizes the encapsulation of both the structure and behavior of objects. By focusing on the contractual responsibilities of a class, the designer is able to postpone implementation considerations until the implementation phase.
While responsibility-driven design is not the only technique addressing this problem, most other techniques attempt to enforce encapsulation during the implementation phase. This is too late in the software life-cycle to achieve maximum benefits.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 75: Conclusion

“The Code-and-Fix Model. The basic model used in the earliest days of software development contained two steps:
:1. Write some code.
:2. Fix the problems in the code.
Thus, the order of the steps was to do some coding first and to think about the requirements, design, test, and maintenance later. This model has three primary difficulties: (a) After a number of fixes, the code became so poorly structured that subsequent fixes were very expensive. This underscored the need for a design phase prior to coding. (b) Frequently, even well designed software was such a poor match to users' needs that it was either rejected outright or expensively redevelopment…”

Barry Boehm (1935) American software engineer

Source: A spiral model of software development and enhancement. (1988), p. 61-62

“Executable UML is designed to produce a comprehensive and comprehensible model of a solution without making decisions about the organization of the software implementation. It is a highly abstract thinking tool to aid in the formalization of knowledge, a way of thinking about and describing the concepts that make up an abstract solution to a client problem.”

Stephen J. Mellor (1952) British computer scientist

Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. 10.

“The GNU GPL was not designed to be ""open source"". I wrote it for the free software movement, and its purpose is to ensure every user of every version of the program gets the essential freedoms.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

""Re: GPL version 4"" on NetBSD mailing list (17 July 2008) http://mail-index.netbsd.org/netbsd-users/2008/07/17/msg001546.html
See http://www.gnu.org/philosophy/open-source-misses-the-point.html for more explanation of the difference between free software and open source.
2000s

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

Help us to complete the source, original and additional information

Paul Graham 43

Related quotes

Related topics