Comments, and opinoins on a classic
Written: May 31 '00 (Updated May 31 '00)
|
Product Rating:
|
|
|
Pros: There is no "everybody" option in the "I recommend this book for" select box
Cons: big reputation, lots of un-substantiated opinion
|
|
|
| menasha's Full Review: Mythical Man Month Essays on Software 2e Books |
This is a classic, most every respectable author will reference this book in his/her bibliography if it has anything to do with software project management. It is responsible for some of the most often quoted phrases in the industry such as "adding more people, to a late project is like adding gas to a fire", or my personal favorite "plan to throw one away". Worth reading this book just to understand what people mean when they refer to "essential complexity". Now that we have established it's importance, and that it is worth reading, here are some points and criticism (You are reading this review for more than just praise I hope).
Frank Brooks falls prey to Microsoft bashing in numerous places thought the book. I think it is rather disgusting to see him follow the masses and poke fun at Windows NT, and MS-DOS. His criticism often comes out of the blue, with little backing, as if we are to nod in approval. He refers to MS-DOS as an example of a system that has consistency of design, yet still lacks clarity and simplicity. He refers to Windows as falling prey to the "Second System Syndrome". (I don't agree the syndrome even exists).
Brooks proposes a perfect small software development team is like a very specialized surgical team in the essay "The Surgical Team". The most important member of the team, being the head surgeon, while the other team members pass him sharp tools, and clean up the blood. While I don't have the experience Brooks has in the industry, I couldn't help but disagree. This is an armchair thesis, never have I seen a team function in this manner, and I don't think it is the best approach to development. Can one man really do all the coding? is one man as backup enough? Where are the checks and balances? For another approach to structuring a team I highly recommend "Extereme Programming" by Kent Beck. It is field tested and flies in the face of what brooks says (and everybody else for that matter).
Don't be afraid if this book was written before you where born, it is still applicable, as he does not deal with any technical topics. At one point when I was looking for a job, I asked all my prospective employers if they had read this book, It was a strike against them is they said "no, never heard of it".
Recommended:
Yes
|
|
|
|
Epinions.com ID:
menasha
|
|
Member: Benjamin Menasha
Location: Somerville MA
Reviews written: 8
Trusted by: 2 members
|
|
|
- Add to My Yahoo!: 
- Add to Google Homepage: 
© 1999-2009 Shopping.com, Inc.