The authors of AntiPatterns draw on extensive industry experience, their own and others, to help define what's wrong with software development today. They outline reasons why problem patterns develop (such as sloth, avarice, and greed) and proceed to outline several dozen patterns that can give you headaches or worse.
Their deadliest hit list begins with the Blob, where one object does most of the work in a project, and Continuous Obsolescence, where technology changes so quickly that developers can't keep up. Some of the more entertaining antipatterns include the Poltergeist (where do-nothing classes add unnecessary overhead), the Boat Anchor (a white elephant piece of hardware or software bought at great cost) and the Golden Hammer (a single technology that is used for every conceivable programming problem). The authors then proceed to define antipatterns oriented toward management problems with software (including Death by Planning and Project Mismanagement, along with several miniature antipatterns, that help define why so many software projects are late and overbudget).
The authors use several big vendors' technologies as examples of today's antipatterns. Luckily, they suggest ways to overcome antipatterns and improve software productivity in "refactored solutions" that can overcome some of these obstacles. However, this is a realistic book, a mix of "Dilbert" and software engineering. A clever antidote to getting too optimistic about software development, AntiPatterns should be required reading for any manager facing a large-scale development project. --Richard Dragan
I'd previously bought the Management Anti-patterns book, which is excellent. There were a couple of references to this book that intrigued me, so I followed up and got this one. Read morePublished 9 months ago by Paul Edwards
Anybody who has ever been in a large group and tried to get something accomplished will appreciate this book. Read morePublished 17 months ago by Amazon Customer
AntiPatterns brings to light a previously unaddressed problem with the way software is currently developed. Read morePublished 17 months ago by Aaron S Vannatter
This book showed me the reality: problems in management and development. And then a solution appears to every problem. These problems repeat again and again over time. Read morePublished on April 18, 2011 by Alexis Henríquez
A must read, in addition to reading "Design Patterns". A good compilation of reasons and events why many software projects fail in our days. Read morePublished on April 24, 2007 by Baskin I. Tapkan
This book starts slowly. I put it down more than once before I got as far as the catalog of anti-patterns. Read morePublished on March 26, 2007 by Greg Klinkel
I bought this book eight years ago in January 1999.
At that time I was employed with a company, which had
several anti patterns in use. Read more
Developers might say that the many chapters in this book about managing (projects) makes it a management book. Read morePublished on November 6, 2005 by Simon Laub
Printed in 1998 this book is likely to have been in the works in 1996-1997, the very beginning of the patterns movement. Read morePublished on July 17, 2005 by Dmitry Dvoinikov