Quote

Plan to throw one (implementation) away you will, anyhow.

Fred Brooks

Change background

T
T
T

Change font

TAGS & TOPICS

Fred Brooks
Age: 93
Born: 1931
Born: April 19
Computer Scientist
Engineer
Mathematician
Software Engineer
University Teacher
Durham
North Carolina
Frederick Phillips Brooks
Jr.
Frederick P. Brooks Jr.
Frederick Phillips Fred Brooks
Jr
Frederick P. Brooks
Frederick Phillips
Plan
Plans
Away
Anyhow
Implementation
Programming
Software
Throw

More quotes by Fred Brooks

Image
The hardest part of the software task is arriving at a complete and consistent specification, and much of the essence of building a program is in fact the debugging of the specification.
Fred Brooks
Image
Systematically identity top designers as early as possible. The best are often not the most experienced.
Fred Brooks
Image
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.
Fred Brooks
Image
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
Image
The bearing of a child takes nine months, no matter how many women are assigned.
Fred Brooks
Image
It is very difficult to make a vigorous, plausible, and job-risking defense of an estimate that is derived by no quantitative method, supported by little data, and certified chiefly by the hunches of the managers
Fred Brooks
Image
The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures.
Fred Brooks
Image
Originality is no excuse for ignorance.
Fred Brooks
Image
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
Image
The boss must first distinguish between action information and status information. He must discipline himself not to act on problems his managers can solve, and never to act on problems when he is explicitly reviewing status.
Fred Brooks
Image
Nine people can't make a baby in a month.
Fred Brooks
Image
The programmer's primary weapon in the never-ending battle against slow system is to change the intramodular structure. Our first response should be to reorganize the modules' data structures.
Fred Brooks
Image
Adding manpower to a late software project makes it later
Fred Brooks
Image
The Waterfall Model is wrong and harmful we must outgrow it.
Fred Brooks
Image
Successful software always gets changed.
Fred Brooks
Image
Even the best planning is not so omniscient as to get it right the first time.
Fred Brooks
Image
Conceptual integrity is the most important consideration in system design.
Fred Brooks
Image
Adjusting to the requirement for perfection is, I think, the most difficult part of learning to program.
Fred Brooks
Image
System debugging, like astronomy, has always been done chiefly at night.
Fred Brooks
Image
Product procedure...must securely protect the crown jewels, but, equally important, it must eschew building high fences around the garbage cans.
Fred Brooks