- Paperback: 336 pages
- Publisher: John Wiley & Sons; 1 edition (20 Mar. 1998)
- Language: English
- ISBN-10: 0471197130
- ISBN-13: 978-0471197133
- Product Dimensions: 19.6 x 2.5 x 24.4 cm
- Average Customer Review: 3.3 out of 5 stars See all reviews (23 customer reviews)
- Amazon Bestsellers Rank: 46,701 in Books (See Top 100 in Books)
- See Complete Table of Contents
AntiPatterns: Refactoring Software, Architecture and Projects in Crisis (Computer Science) Paperback – 20 Mar 1998
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your e-mail address or mobile phone number.
More About the Author
From the Author
Knowing when to apply patterns is critical.
AntiPatterns tries to help the practitioner identify when and how to apply a pattern by recognizing the symptoms of a bad pattern (AntiPattern). The refactored pattern deals with both the symptoms and the root cause. We use many recognized and successful patterns from the patterns community who have been very supportive in getting this book 'out the door'. We attempt to make the whole process fun and easy to use. This is just the start of AntiPatterns and we wish to get people energized in using them and developing new ones.
From the Back Cover
"The AntiPatterns authors have clearly been there and done that when it comes to managing software development efforts. I resonated with one insight after another, having witnessed too many wayward projects myself. The experience in this book is palpable." –John Vlissides, IBM Research "This book allows managers, architects, and developers to learn from the painful mistakes of others. The high–level AntiPatterns on software architecture are a particularly valuable contribution to software engineering. Highly recommended!" –Kyle Brown Author of The Design Patterns Smalltalk Companion "AntiPatterns continues the trend started in Design Patterns. The authors have discovered and named common problem situations resulting from poor management or architecture control, mistakes which most experienced practitioners will recognize. Should you find yourself with one of the AntiPatterns, they even provide some clues on how to get yourself out of the situation." –Gerard Meszaros, Chief Architect, Object Systems Group Are you headed into the software development mine field? Follow someone if you can, but if you′re on your own–better get the map! AntiPatterns is the map. This book helps you navigate through today′s dangerous software development projects. Just look at the statistics:
∗ Nearly one–third of all software projects are cancelled.
∗ Two–thirds of all software projects encounter cost overruns in excess of 200%.
∗ Over 80% of all software projects are deemed failures.
While patterns help you to identify and implement procedures, designs, and codes that work, AntiPatterns do the exact opposite; they let you zero–in on the development detonators, architectural tripwires, and personality booby traps that can spell doom for your project. Written by an all–star team of object–oriented systems developers, AntiPatterns identifies 40 of the most common AntiPatterns in the areas of software development, architecture, and project management. The authors then show you how to detect and defuse AntiPatterns as well as supply refactored solutions for each AntiPattern presented.
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
While some of the anti-patterns are mildly useful -- particularly the ones specifically related to software development itself -- the ones related to project management are so obvious and general that all but the novice will roll his or her eyes back with disbelief that these could be included in a software engineering book.
For instance, the "Corncob Pattern" is a difficult person who causes problems through destructive behaviors and how to work around him or her. It's true that we all run into people like this, but this is supposed to be a book at least _somewhat_ related to software.
They have three patterns that essentially deal with overplanning ("Analysis Paralysis", "Death by Planning", and "Design by Committee"), and while I suppose these are possible, too little planning is much more likely to cause project debacle than too much. In fairness, they do have a not-enough-planning pattern, "Architecture by Implication", though this deals with architecture and not requirements.
Believe it or not, "Irrational Managment" is a "pattern" in an engineering book that discusses what to do if your boss is the problem. This seems to be a topic best left to Dr. Laura, in "Ten Stupid Things Managers Do To Mess Up Your Project".
I was unfortunate enough to read "Anti-Patterns" before "Design Patterns", and the poor quality of the former nearly kept me from reading the latter. These books are simply not in the same league, and some might say not even in the same industry.
Avoid this book unless you have very little real-world experience in the software business.
An antipattern is a pattern that has negative consequences when applied. This ranges from the antipattern that almost always leads to a negative consequence to those that are generally positive, but lead to negative results when used in the wrong context. One example is the Cut-and Paste Programming antipattern. We all have benefited from the use of cut and paste and we have all suffered when we used it in an inappropriate situation. Many such examples are given, and fortunately for us all, for each antipattern the authors provide instructions on how to recognize it, what causes it and how to cure it. Anyone who has worked in software development has experienced one or more of these problems.
In keeping with a negative often being more significant than a positive, it is quite possible that the study of antipatterns will yield more substantial results than similar effort being expended elsewhere. That is why I included this book in my list of best books of the year that appeared in the September, 1999 issue of _Journal of Object-Oriented Programming_.
I have never enjoyed reading about the foibles of software development and software project management than reading the AntiPatterns book.
Not only does this book tell you about a number of AntiPatterns, but you also get Patterns or refactored solutions to deal with the AntiPatterns.
I just skimmed the introductory chapters, so I could get to the meat of the book: the AntiPatterns. As you read through them, you will be nodding your head. Quite a number of them are just plain common sense. However, if you have not "Been there, done that", you will truly appreciate them.
I also like the fact they have AntiPatterns at all levels of Software Development. From the Blob: a CLASS that does it ALL, to the CORNCOB: the individual who says: "We must use CORBA". This book will be useful for all participants from the developer to the Project Manager.
I congratulate the authors on an informativ! e and entertaining book!
Most Recent Customer Reviews
Probably the most pointless and boring book on IT I have encountered in the 40 years since I first learned to program (in FORTRAN on the University mainframe). Read morePublished 6 months ago by Tom Rose
Reviews for "Patterns" books always seem to be highly polarised - "buy it!"/"burn it!".
So, let's be clear about (my opinion of) the purpose of Patterns: it is to generalise... Read more
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 12 Aug. 2001
Perhaps the title of this book is unfortunate, given the fact that those who have posted bad reviews here seem to have expected it to be an extension of the GoF Design Patterns... Read morePublished on 19 Aug. 1999
If only all the compter lit I have to read was this great. Some guys in class said it's just a "rehash of well-known computer mistakes like Spaghetti Code. Read morePublished on 11 Jun. 1999
This book was quite a disappointment, especially since I heard so much about it. As Shakespeare said "There is nothing new under the sun" and this book proves it. Read morePublished on 13 May 1999
Being able to identify and name key problems in a software project is as helpful (if not more) as being able to design it well. Read morePublished on 27 April 1999
After reading the reviews here on Amazon, I simply had to find out what it was about AntiPatterns that so polarized people.
I'm glad I did. Read more
Very little content. No evidence. Buzz words without substance. Poorly written. not very helpful.
Spend your money elsewhere.