Fred Brooks: Design

Fred Brooks is American computer scientist. Explore interesting quotes on design.
Fred Brooks: 40   quotes 0   likes

“The term architecture is used here to describe the attributes of a system as seen by the programmer, i. e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture”

Fred Brooks

Gene Amdahl, Gerrit Blaauw, and Fred Brooks (1964) "Architecture of the IBM System." in: IBM Journal of Research and Development Vol 8 (2) p. 87-101.

Behavior

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

Parting

“… the organization chart will initially reflect the first system design, which is almost surely not the right one [… ] as one learns, he changes the design [… ]. Management structures also need to be changed as the system changes…”

Fred Brooks

The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

Learning , Change

“Study after study shows that the very best designers produce structures that are faster, smaller, simpler, clearer, and produced with less effort. The differences between the great and the average approach an order of magnitude.”

Fred Brooks No Silver Bullet

Page 202.
No Silver Bullet (1986)

Effort , Study

“The "Second System Effect":
An architect’s first work is apt to be spare and clean. He knows he doesn’t know what he’s doing, so he does it carefully and with great restraint.
As he designs the first work, frill after frill and embellishment after embellishment occur to him. These get stored away to be used “next time.” Sooner or later the first system is finished, and the architect, with firm confidence and a demonstrated mastery of that class of systems, is ready to build a second system.
This second is the most dangerous system a man ever designs. When he does his third and later ones, his prior experiences will confirm each other as to the general characteristics of such systems, and their differences will identify those parts of his experience that are particular and not generalizable.
The general tendency is to over-design the second system, using all the ideas and frills that were cautiously sidetracked on the first one. The result, as Ovid says, is a "big pile."”

Fred Brooks

Page 55.
The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

Confidence , Idea , Time , Parting

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

Passion , Parting

“Job Control Language is the worst programming language ever designed anywhere by anybody for any purpose.”

Fred Brooks

http://www.youtube.com/watch?v=8c0_Lzb1CJw#t=01h19m00s
"The IBM System/360 Revolution"
recorded by the Computer History Museum
April 7, 2004.

“Einstein repeatedly argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. Much of the complexity he must master is arbitrary complexity [… ] because they were designed by different people, rather than by God.”

Fred Brooks No Silver Bullet

Page 184.
No Silver Bullet (1986)

God , People , Faith , Nature