The Mythical Man-Month. Essays on Software Engineering [Englisch] [Taschenbuch]

In 1975, Frederick P. Brooks, Jr. wrote a ground breaking insightful book about computer science. He accurately captured someof its more esoteric aspects and relayed them in a colorful narrative. I especially liked his use of the illustrations and quotations as the opening of each chapter. Each was thoughtfully chosen and served to set the tone for the following text.

Also entertaining is Brooks' use of the analogy. In the section using the tar pit to describe the struggle faced during large system programming, one comes away saying, "Been there, seen that!" This technique draws you in and makes you want to read on.

Readers of this book will find themselves looking at computer science differently. No longer will it be just a science. The philosophical and artistic values will become clear. Brooks' holistic approach may very well sway some readers toward a more pensive view of computer science. At the very least, the reader should come away with a deeper appreciation for software engineering.

My only negative commentary would be with the added chapters. While the insight gained over twenty years is useful, it comes off as a little defensive. It's almost as if the passion which so beautifully captured the message in the 1975 version, was spent on defending twenty year old statements. I suspect that the author might argue that he was trying to be systemic and clear. In my opinion this came off as overkill. To borrow an old argument, maybe Dr. Brooks fell victim to the "Second-System Effect" of which he so vividly warns us.

Topics first brought to light by this book and still highly relevant today include the concept that good software tools will always save you time, money and staff, and that productivity for software engineers is inversely proportional to the amount of administrative work they need to do.

Read this book whenever management wants to save money by scrimping on your development environment.

This "Anniversary" edition includes some additional material, as well as the author's commentary on what has changed -- and what has not. Even that which no longer applies is educational, in that it shows us how things have evolved. But by and large, most of what Mr. Brooks wrote back in 1975 still applies in 2000.

Those who do not know history are doomed to repeat it. If you are involved in software engineering, you will need to know what this book talks about. You might as well read it now, rather then finding out the hard way.