Binding: Paperback Dewey Decimal Number: 005.1068 EAN: 9780201835953 ISBN: 0201835959 Label: Addison-Wesley Professional Manufacturer: Addison-Wesley Professional Number Of Items: 1 Number Of Pages: 336 Publication Date: August 12, 1995 Publisher: Addison-Wesley Professional Sales Rank: 3968 Studio: Addison-Wesley Professional
Amazon.comThe classic book on the human elements of software engineering. Software tools and development environments may have changed in the 21 years since the first edition of this book, but the peculiarly nonlinear economies of scale in collaborative work and the nature of individuals and groups has not changed an epsilon. If you write code or depend upon those who do, get this book as soon as possible -- from Amazon.com Books, your library, or anyone else. You (and/or your colleagues) will be forever grateful. Very Highest Recommendation.
Customer Reviews
Average Rating:
Rating: - Excellent & Highly Recommended Book
I have read this book twice now. Once in college and once again now 5 years later. While I did not get much out of it 5 years ago, now that I have been in the industry a few years, it is a VERY good re-read.
Rating: - Required Reading For Anyone Serious About Software Development
30 Years later this book is still highly relevent. If your project is in trouble, don't add bodies!
Rating: - seminal classic
Fred Brooks, the author, is the individual primarily responsible for the IBM System/360, arguably the most successful computer software system built to this point. He is also primarily responsible for the IBM OS/360, which was not as successful. You may find that his frank and honest assessment of why one was successful and one was not provides a map of a right way to develop software and an alert system for what can go wrong. Because of this and the distilled thought and experience present in ... Read More
Rating: - A insightful book about software project development
I have been a software project manager for many years. One of the biggest problem that I encountered was what the author called as "Second System Effect". Some times, architects were unable to discipline himself to avoid over-designing systems in the second project. Their goals were to build perfect systems that would streamline all processes without considering the costs and patience of business groups. To convince others that they were right, they could come up with various reasons that sounded ... Read More
Rating: - A must-read for project leads in the software industry
An excellent book and a must-have for all those involved in the software industry. The concepts and problems described in this book are still valid to this day in our modern software development process.
I recommend this book to everyone active in the field of software development.