7 of 7 people found the following review helpful:
5.0 out of 5 stars
Prophetic -- but of its time, December 20, 1999
This review is from: The Mythical Man-Month: Essays on Software Engineering (Paperback)
There really are very few software engineering books written in 1975 that are worth reading today. Brooks remains powerful stuff because large system projects are still often disastrous. We are not often bothered by the flowcharts that Brooks dislikes, but the disorganized projects, endless meetings, problems of scaling, unhelpful documentation and inflexible systems are certainly still with us.
I was struck recently by the parallels with Kent Beck's Extreme Programming: Brooks had in his way foreseen much of what this recent movement has been urging.
Brooks' classic book underlies much systems engineering thinking, and his example along with the frightening story of OS/360, enlivened with Brooks' inimitable anecdotes and illustrations, remains essential reading.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
2 of 2 people found the following review helpful:
5.0 out of 5 stars
Must read for anyone dealing regularly with complexity., October 12, 1997
By A Customer
This review is from: The Mythical Man-Month: Essays on Software Engineering (Paperback)
This is a classic tale of managment philosophy and software engineering. It contains some of the best descriptions of human behavior and engineering intuition ever distilled into book format. A must read for anyone managing, or working on, complex projects of any sort.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
5.0 out of 5 stars
A good, undying, informative, inspiring and enjoyable read!, October 16, 2010
This review is from: The Mythical Man-Month: Essays on Software Engineering (Paperback)
I learned by my own mistakes the meaning of the expression, "You can pay me now or pay me later." There are few or sometimes no short-cuts in software or hardware development or engineering, or electronics in general. Fred Brooks, best known as the "father of the IBM System 360," and after 30 years still holds the title of the most influential book on software project management, likened it to pregnancy. He said you can add all the women you want "to the project" and still, it will take nine months! That's why, in managing software development projects, I learned to spend ample time with the software developers beforehand. Otherwise, I would inevitably spend the time with them afterwards. I was the one knowing the design. I had the "big picture" that needed to be communicated to them.
In his book, Brooks described the foibles of the early design teams and programming at IBM. From his own mistakes, he came up with snappy principles like "If you don't have time to do it right the first time, when will you find time to do it over?" He also coined what became known as the "Second-System Approach," which basically said "by the time you finish developing a system, you know what you should have done"--therefore, throw it away and start from scratch again. He identified the corruptible optimism of good intentions that truly but erroneously believed, for most of the project, that the work was 90% done or that debugging was 99% done most of the time. He insisted, "Ask whenever there's a doubt. NEVER assume anything."
This book is filled with timeless development advice by a master from a previous age. The advice, however, is as valuable now as it was then.
A good, undying, informative, inspiring and enjoyable read!
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No