“How a designer gets from thought to thing is, at least in broad strokes, straightforward: (1) A designer conceives a purpose. (2) To accomplish that purpose, the designer forms a plan. (3) To execute the plan, the designer specifies building materials and assembly instructions. (4) Finally, the designer or some surrogate applies the assembly instructions to the building materials. What emerges is a designed object, and the designer is successful to the degree that the object fulfills the designer's purpose”

— William A. Dembski

Opening words of [No Free Lunch: Why Complexity Cannot be Purchased Without Intelligence, Lanham, Md., Rowman & Littlefield, 2002, 0742512975, http://www.arn.org/docs/dembski/wd_nfl_intro.htm, Preface]
2000s

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 "How a designer gets from thought to thing is, at least in broad strokes, straightforward: (1) A designer conceives a pu…" by William A. Dembski?

William A. Dembski photo

William A. Dembski 27

American intelligent design advocate 1960

Related quotes

“One could describe Design as a plan for arranging elements to accomplish a particular purpose.”

Charles Eames (1907–1978) American designer, half of duo the Eames

In answer of the question: What is your definition of Design?
Design Q & A with Charles Eames, 1972

“Marketing management is the analysis, planning, implementation, and control of programs designed to create, build, and maintain beneficial exchanges with target buyers for the purpose of achieving organizational objectives.”

Philip Kotler (1931) American marketing author, consultant and professor

Philip Kotler (1993), as cited in: Gerald A. Cole (2003), Strategic Management, p. 131

“Computer-aided design is not automatic design, although it must include many automatic design features. By automatic design we mean design procedures which are capable of being completely specified in a form which a computer can execute without human intervention.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Computer-Aided Design: A Statement of Objectives (1960), p. 2.

“If the design takes too long to build, it’s a bad design.”

Elon Musk (1971) South African-born American entrepreneur

Source: https://qz.com/1718402/elon-musk-says-his-starship-will-fly-to-orbit-in-six-months/
Context: If the design takes too long to build, it’s a bad design. If the schedule is long, it’s wrong; if it’s tight, it’s right.

“Experienced object designers explore the design space from many different angles. They refine ideas of how their system should respond while they are in the middle of building and discarding ideas about how their design should work. Getting a design to gel involves making assumptions, seeing how they play out, changing one’s mind or perspective slightly and re-iterating. Design is a difficult, involved task. It inherently is a non-linear process. Yet, we are asked to trace our design results back to system requirements. And, if we uncover some implications during design, we’d like to tune our system requirements to reflect necessary design compromises.”

Rebecca Wirfs-Brock (1953) American software engineer

Abstract
Designing scenarios: Making the case for a use case framework (1993)

“Architects know that some kinds of design problems are more personal than others. One of the cleanest, most abstract design problems is designing bridges. There your job is largely a matter of spanning a given distance with the least material. The other end of the spectrum is designing chairs. Chair designers have to spend their time thinking about human butts.”

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

"Five Questions about Language Design" http://www.paulgraham.com/langdes.html, May 2001

“Responsibility-driven design specifies object behavior before object structure and other implementation considerations are determined. We have found that it minimizes the rework required for major design changes.”

Rebecca Wirfs-Brock (1953) American software engineer

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

“Object-oriented design is a method of design encompassing the process of object-oriented decomposition and a notation for depicting both logical and physical as well as static and dynamic models of the system under design.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 37

“The objective of the Computer-Aided Design Project is to evolve a machine systems which will permit the human designer and the computer to work together on creative design problems.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Computer-Aided Design: A Statement of Objectives (1960), p. iii: Abstract.

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

Related topics