Some people have called the book the "bible of software engineering". I would agree with that in one respect: that is, everybody quotes it, some people read it, and a few people go by it.
Fred Brooks Carolinian
Source
As quoted in Quoted Often, Followed Rarely, ; About the 1975 The Mythical Man-Month.
- year
- 1975
Cite this record
“Some people have called the book the "bible of software engi…” Fred Brooks. Carolina Quotes, record CQ-A0BBCF9419. https://carolinaquotes.com/quote/a0bbcf9419
More from Fred Brooks
Brooks's Law: Adding manpower to a late software project makes it later.
…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…
…well over half of the time you spend working on a project (on the order of 70 percent) is spent thinking, and no tool, no matter how advanced, can think for you. Consequently, even if a tool did everything except the thinking for you – if it wrote 100 percent of the code, wrote 100 percent of the documentation, did 100 percent of the testing, burned the CD-ROMs, put them in boxes, and mailed them to your customers – the best you could hope for would be a 30 percent improvement in productivity. In order to do better than that, you have to change the way you think.