If patterns are good ideas that can be re-applied to new situations, AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis looks at what goes wrong in software development, time and time again. This entertaining and often enlightening text defines what seasoned developers have long suspected: despite advances in software engineering, most software projects still fail to meet expectations--and about a third are cancelled altogether.
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
Patterns are popular in software development and used to identify different types of procedures, designs, or codes that work. AntiPatterns are the exact opposite. They target common mistakes, errors, and people issues that can cause a software project to fail. Despite its negative sounding name, the positive benefits of AntiPatterns are enormous. This book discusses what AntiPatterns are and then provides practical guidelines on how to detect AntiPatterns and the refactored solutions that correct them. The authors discuss over 40 different AntiPatterns in the areas of software development, architecture, and project management.See all Product Description
I was very anxiuos about reading this book. Before of purchasing it, I had already read some info and presentations on the web (c2 wiki, antippaterns site, etc.). Read morePublished on Jan. 23 2004 by Leon Exequiel Welicki
I picked up this book at one of the few remaining good bookstores that caters to IT professionals and found it an enjoyable read. Read morePublished on July 27 2003 by Ask Doctor Java
This book basically explains to managers how their development team screws up. The examples of how to fix the problems are too basic. Read morePublished on July 9 2002 by D. Hicks
- This book is on process and *NOT* architecture.
- It is for managers and not for developers. Read more
Like practically all books on patterns I encountered so far this book doesn't lent itself easily to reading cover to cover and its difficult to use as a reference book without... Read morePublished on Aug. 17 2001 by ws__
The material in this book is unbelievably superficial and reeks of the authors' pretentiousness. It is referenced frequently in the pattern literature, but don't go anywhere near... Read morePublished on Aug. 12 2001
I found some value in AntiPatterns for the comprehensive collection of "common pitfalls" that it describes; but it is otherwise seriously disappointing. Read morePublished on March 16 2001 by Laurent Bossavit
A noble effort, but this book fails to sufficiently build upon existing literature. Steve McConnell's _Code Complete_ and _Rapid Development_ do a better job covering similar... Read morePublished on Jan. 28 2001 by Zig Zichterman