AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
||Author: William J. Brown, Raphael C. Malveau, Hays W. "Skip" McCormick, Thomas J. Mowbray|
List Price: $44.99
Our Price: Click to see the latest and low price
Publisher: John Wiley & Sons (20 March, 1998)
Sales Rank: 81,045
Average Customer Rating: 3.22 out of 5
Customer ReviewsRating: 2 out of 5
A good idea, a very boring and dissapointing implementation
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.). I already knew the catalog and i'd like it very much.
But the book...what can i say of the book? first of all, I found it quite boring and verbose. The same could have been sayed using half of the words or maybe less...
In the book I've found a couple of annoying things:
- The authors quote themselves ALL the time
- The solution to ALL architecture antipatterns (and software as well) includes a reference to CORBA, OMG IDL or open systems...There are more things in the world! What can we, developers in sin, that don't use open systems or corba do?!?!
- They never do quote the GoF work, altough in same cases it would be very helpful, instructive and fair. In turn, they quote to their CORBA patterns book
- They only quote the GoF to say that their patterns are complex and that antipatterns are easier and funnier. Couldn't disagree more on this!
- There are some contradictory ideas throughout the book
- They are doing themselfs in some of the antipatterns (I would not say which ones, but after a quick read is easy to guess ;))
- The second chapter, the reference model, is very boring and with lots of unnecesary rethoric
- In fact, all the book is full of unnecesary and unpleasant rethoric stuff
- After reading the book from cover to cover, I realized that just reading the "Appendix A" I would had enough
- The name of the book is tricky. They don't say nothing about CORBA, but inside the book they say that this is the companion book of "CORBA Design Patterns"
- Many of the solutions are biased
- Their concept about refactoring is quite "fuzzy"...
There are some good points on the book:
- The catalog is quite interesting.
- Some patterns are nicely developed and fun to read
- Being familiar with the catalog allows to find easily antipatterns in everyday work
- The final appendix is a very nice compilation that offers a good view to the catalog
Anyway, the point is: don't buy this book. You can get the same in the web for free, saving money and time
Rating: 5 out of 5
Joy and Pain
I picked up this book at one of the few remaining good bookstores that caters to IT professionals and found it an enjoyable read. Some may be turned off by the book as it does contain some highly speculative statements that are not supported by facts. For those who refuse to remove the stick from their XXXX then don't buy this book.
For those who want a good read on the IT profession as a whole, then I recommend it. If you enjoy Dilbert, you will enjoy this one as well.
Rating: 1 out of 5
Skip it - poorly written; little substance
I've gotten a lot of milage out of the GoF Design Patterns book, but like many people, I have seen software where design patterns were applied inappropriately. I was looking for a book that explored some common pathologies of Patterns-based design and suggested appropriate refactorings to overcome them.
Sadly, this book is not the one I was looking for. Large amounts of the book are filled with mindless jargon, or would be better aimed at managment consultants than software engineers. The authors have a bizarre obsession with CORBA, and several of the "antipatterns" seem to be little more than a personal rant about failed CORBA projects the authors have been involved with.
Worse, the antipatterns that discuss software rather than organizational issues are often so poorly written that they are useless. Often they are written in such vague language that you can't figure out what type of system is being discussed. The problem is compounded by facile examples that don't clearly illustrate the problem or the possible solution. The authors can't even manage a clear definition & example of "Spaghetti Code", which any 1st year engineer has probably encountered.
SAVE YOUR MONEY. I'd recommend reading GoF's Design Patterns and Martin Fowler's Refactoring instead of this book.
· Refactoring: Improving the Design of Existing Code
· Extreme Programming Explained: Embrace Change
· Design Patterns
· AntiPatterns in Project Management
· Patterns of Enterprise Application Architecture