AntiPatterns
and over one million other books are available for Amazon Kindle .
Learn more
| ||||||||||||||||||||
 Trade In this Item for up to £0.25
Trade in AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis: Refactoring Software, Architecture and Projects in Crisis for an Amazon.co.uk gift card of up to £0.25, which you can then spend on millions of items across the site. Plus, get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
Product Description
Product Description
"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.
∗ 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.
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.
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.
Inside This Book
(Learn More)
First Sentence
AntiPatterns represent the latest concept in a series of revolutionary changes in computer science and software engineering thinking. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
AntiPatterns represent the latest concept in a series of revolutionary changes in computer science and software engineering thinking. Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
6 of 6 people found the following review helpful
Format:Paperback
The patterns start in chapter five. Ignore the rest of the book on pain of absolute boredom. For example chapter two (32 pages) defines the keywords to be used in catagorising the patterns. Chapter three (9 pages) defines all the ways that patterns are ever written up, probably in order to justify changing it in this book. I notice that most or all the good reviews are by management and consultants, so maybe it works better for them, but I found the engineering antipatterns too few in number and too obvious in solution. Instead try Deathmarch Projects, Writing Solid Code, and Debugging the Development Process. They don't have the magic word "pattern" in the titles, but they're a lot more use.
Format:Paperback
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 just enough to be identifiable & helpful.
This book does that, and uniquely, does it at 3 levels of applicability: so it has help for coders, architects and managers.
The best unique feature is that it helps you decide what NOT to do - a critically important decision! (And how to back-pedal if it's too late...)
Whichever of the roles above you hold, and especially if you've moved between them, this book will give you helpful perspectives on fixing problems you and your colleagues will meet in organisations of 1 or more people.
So, let's be clear about (my opinion of) the purpose of Patterns: it is to generalise just enough to be identifiable & helpful.
This book does that, and uniquely, does it at 3 levels of applicability: so it has help for coders, architects and managers.
The best unique feature is that it helps you decide what NOT to do - a critically important decision! (And how to back-pedal if it's too late...)
Whichever of the roles above you hold, and especially if you've moved between them, this book will give you helpful perspectives on fixing problems you and your colleagues will meet in organisations of 1 or more people.
Format:Paperback
This book tries to follow on the success of the wonderful book Design Patterns (Gamma, et. al.) but fails miserably. It's been said in other reviews that this is "common sense packaged as wisdom", and this is not far from the mark.
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.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Most Recent Customer Reviews
DO NOT BUY THIS BOOK!
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 more
Published on 12 Aug 2001
An enjoyable, usable guide to project management
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 more
Published on 19 Aug 1999
My New Favorite "Work" Book
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 more
Published on 11 Jun 1999
Common Sense sold as wisdom
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 more
Published on 13 May 1999
Very nice book, enjoyable and instructive
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 more
Published on 27 April 1999
Communicates complex ideas simply and captivatingly!
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
Published on 20 April 1999
didn't like the book - don't bother
Very little content. No evidence. Buzz words without substance. Poorly written. not very helpful.
Spend your money elsewhere.
Published on 9 April 1999
Pleasurable Read
This is a great read. Almost every paragraph had me thinking back to some real-life incident. Funny as hell.
Published on 23 Mar 1999
So So
This one is okay but far from great. Mowbray's books make a few good points but you have to wade through way too much fluff. Straight and to the point works best for me. Read more
Published on 20 Mar 1999
Great title, awful book
Like Mowbray's other abomination, "Corba Design Patterns", this book has a really catchy title, but almost no meaningful content at all. Read more
Published on 9 Mar 1999
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
