In fact, this was the first major book to accurately assemble the knowledge needed to engineer a large software project into one place, and relate it from the perspective of a finished project.
These essays alone are worth reading, as they give an accurate estimate of where the industry is now. There's no particularly good reason, they just are too busy reading the latest book on today's fad.
The irony, of course, is that today's fad will be laughed at next year, while will still be around a decade from now. What does project management matter to a bunch of semi-organized groups?
C is a blip on the horizon, just starting to make its way out of Bell Labs.
Assembly language is still widely used throughout the industry.
Surgical development teams, the second-system effect, and the importance of documentation are all covered, sometimes for the first time, in .
Through the course of the book, Brooks covers all fascets of what must happen to successfully complete a major software project, and in all parts he gives a firm foundation for solid software engineering and project management.
If you were assigned this book in school, read it again (you probably didn't the first time :-). Aren't we doing fine as it is in our striving for World Domination? On one hand, we don't have the pressures of commercial software.
If Apache comes out tomorrow instead of today, no matter.
We don't have too many projects with lots of different architects.
On the other hand, we've been blessed with low expectations.