my dog learned polymorphism*
The moose likes Book Reviews and the fly likes Anti-Patterns / Refactoring Software, Architectures, and Projects in Crisis Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Books » Book Reviews
Bookmark "Anti-Patterns / Refactoring Software, Architectures, and Projects in Crisis" Watch "Anti-Patterns / Refactoring Software, Architectures, and Projects in Crisis" New topic
Author

Anti-Patterns / Refactoring Software, Architectures, and Projects in Crisis

Book Review Team
Bartender

Joined: Feb 15, 2002
Posts: 926
<pre>Author/s : Brown, Malveau, McCormick, and Mowbray
Publisher : Wiley
Category : Design
Review by : Mark A. Herschberg
Rating : 7 horseshoes
</pre>
If you like pattern books, you'll like Anti-Patterns. What is an anti-pattern? It's a design pattern for bad code. Let's face it, we all see plenty of bad code on the job, this book will help you better identify it.
This book, like a pattern book, is a catalog. Each anti-pattern definition is structured like a pattern: Name, Root Causes, Symptoms, Consequences, Anecdotal Evidence, and Refactored Solution. It identifies what the problem is, along with its causes. It goes on to discuss the consequences of the problem and then discusses the refactored solution. As with a pattern definition, it goes into great detail, including such information as exceptional cases. The book contains 3 categories of anti-patterns: software development anti-patterns, software architecture anti-patterns, and project management anti-patterns.
The book itself is easy to read. It's entertaining, too, often written with a tongue in check style. The anecdotal evidence provided for the anti-patterns is something right out of Dilbert, funny and accurate.
The best review I can give is to name some of the anti-patterns from the book: Lava Flow, Golden Hammer, Spaghetti Code, Stovepipe System, Vendor Lock-in, Fire Drill. Like regular design patterns, you probably recognize some of them, but will be able to better identify and apply the knowledge after seeing it formally treated.
Exposure to anti-patterns is just as important as exposure to design patterns. This book is a good introduction to the subject.
More info at Amazon.com || More info at Amazon.co.uk
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Anti-Patterns / Refactoring Software, Architectures, and Projects in Crisis
 
Similar Threads
Bitter Java
Pattern Oriented Software Architecture, Vol 1.
J2EE AntiPatterns by Bill Dudney, Stephen Asbury, Joseph K. Krozak, Kevin Wittkopf
Designing Interfaces by Jenifer Tidwell
Software Architecture Design Patterns in Java by Partha Kuchana