|
|
|
|
| ISBN10: 0471197130 |
| ISBN13: 9780471197133 |
| Publisher: John Wiley & Sons |
| Pubdate: 03-98 |
| Pages: 416 |
| Weight: 2 lbs |
| List Price: $55.00 |
| Discount: 20% | | You Save: $11.00 |
| CBO Price: $44.00 |
|  |
Anti-Patterns
Refactoring Software, Architectures, and Projects in Crisis
by William Brown, Hays W. McCormick, III, and Thomas Mowbray
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. Anti-Patterns are an emerging and controversial new area in the Patterns Community.
Where design patterns identify different types of procedures, designs, or code that WORKED in object-oriented projects, Anti-Patterns target those common mistakes, defects, or errors that can sink object-oriented projects and systems.
The Anti-Patterns movement has stirred up some controversy within the Patterns area because of
1.) the negative-sounding name and
2.) many Anti-Patterns supporters fail to provide practical advise on how to deal with these errors and defects after they are detected.
A book that discusses what Anti-Patterns are and also provides concrete guidelines on what to do once the patterns are detected, will be of interest to both supporters and critics of anti-patterns.
Software developers and programmers will be able to use this book as a constant resource of design errors or defects that are common to object-oriented system development.
The authors will discuss 40 different Anti-Patterns. For each pattern covered, the authors will provide a solution to the anti-pattern, why it occurs, and a case study where that solution worked. Patterns that are related to each other will be cross referenced.
| Have
you read this book? |
 Write
a Review |
Did you love it? Hate it?
Write the first original CBO review for this book, and let others
know what you thought about it! |
|
Amazon Reviews: Average Rating: 3.0
| lots of good stuff |
(4/24/2007)
|
A must read, in addition to reading "Design Patterns". A good compilation of reasons and events why many software projects fail in our days. Also recommend reading "How to Fail At Software Development" to compliment this. There are also a few "Design Patterns" books, including the GoF's, and the blonde skinny girl cover "Head-First" series. Looking forward to discussing the anti-patterns with co-workers to disseminiate the info. I assume every software dev. type person read "Code Complete", right? |
|
| worth a read |
(3/27/2007)
|
This book starts slowly. I put it down more than once before I got as far as the catalog of anti-patterns. Once there, I found some useful information on what goes wrong with software projects and how to address the problem areas.
I would characterize this book as "experiences with software engineering" in general. There is a fair amount on architectural principles, design, and even management topics that were worth the read. |
|
| helps to improve situation in software projects |
(1/23/2007)
|
I bought this book eight years ago in January 1999.
At that time I was employed with a company, which had
several anti patterns in use. Using this book I was able
to improve the situations by having constructive discussions
with the CEO.
The book is structered into three parts; these are Software Development,
Software Architecture and Project Management AntiPatterns. The technical
examples given in the first two parts are quite outdated. Since the first
release of the book more developers have knowledge about object oriented programming.
Therefore the part about software development has lost some of its benefit.
However, the third part about project management is still valid today.
Although the content is humorous, it is constructive as it offers
advice on how to change the condition. Every patterns contains
a section titled "Refactored Solution", which explains how the problem
can be resolved. If you are a developer in a company and you recognize
anti patterns in your project, the first thing you need to do is to
tell your manager that a problem exists. And this is the most difficult
part as most manager might deny that problems exist in their projects. But
once you and your manager agree on that, it should be possible to apply
the refactored solution.
This book also allows you the judge the quality of the company you work
for. If you see plenty of anti patterns in your company and none of the manangers
is willing to recognize their existence, look for new employment opportunities.
I don't give this book the maximum number of points as some of its content is
not up to date any more. The authors should consider revising the first
two parts about software development and software architecture. |
|
| The dark side of software development |
(11/7/2005)
|
Developers might say that the many chapters in this book about managing (projects) makes it a management book. Managers on the other hand, might think that chapters on software code review, and stuff like that, is not relevant for them.
In my view, both managers and developers would be wrong.
Surely, developers should know about management of large software projects, just as managers should have a feel for technical details in a software project. Without this knowledge (of what other people are supposed to be doing) surely software projects are in for bad times.
So, in my view this kind of book should be read by both management and developers. Knowing these anti patterns (the problem) is the first step in avoiding them.
And I think the book does an excellent job in describing the anti patterns.
Not so sure about the solutions though. Ok, projects are managed bad, systems are designed bad, code is written bad. And its fun to read about - if you don't have the particular problem yourself - But as other reviewers have written, something clearly has to do with human nature and not just work procedures.
Anyhow, the book should make you think about what is going on (in your project) - and thats a good thing.
-Simon
|
|
| And the next thing you know your momma is a pattern |
(7/18/2005)
|
Printed in 1998 this book is likely to have been in the works in 1996-1997, the very beginning of the patterns movement. A scientifically important step, possibly, but not worth the book. A tendency to find patterns in everything (Golden Hammer is it ?) has played a cruel joke - the book is an anti-pattern in itself.
All that you will learn by reading this book is that software development is in big trouble and nothing could save it. Projects are managed bad, systems are designed bad, code is written bad. But what's the force behind that ? Human nature, that's what ! Seven sins literally are being blamed for the software problems.
Look, I _fully_agree_, but what's the point in finding the funny called patterns in human behavior ? It sure happens in all industries (patterns themselves came from architecture after all), and shouldn't we be reading psychology instead ?
Now, let's see, how the (IT) books should not be written no matter what:
- No observable structure in content, on either book, chapter or page level. So much dust, nothing sticks.
- Written by a committee of admittedly high professionals, this book is ignorant to the audience. Names for the patterns are likely to be taken from their own academic environments, and not only they frequently have no universal meaning (ex. Lava Flow or Cover Your Assets), but worse - the reader is expected to know the English folklore of rather specific sort. As I'm not a native English speaker, I wouldn't know what a Blowhard Jamboree (or The Grand Old Duke Of York) is unless I look in the dictionary. And what are the chances that I come up with this name later when I need to recall the familiar looking anti-pattern ?
- Layout and formatting looks like it's been quickly put up and had no designer to it. Tables and diagrams that look similar or identical although the underlying matter they are explaining is completely different. Pictures are ugly (although comical) and share no style.
- The appendix dictionary of patterns following the book contains, say, 50 assorted items coming from different areas and they are put in alphabetical order for God's sake.
There probably are better anti-patterns books by the time of this review, then you'd better get them instead. |
|
 More Reviews...
|
|
|
|
|
|
|
|
|
|
Copyright © 1997-2009 Computer Books Online
|
|
|
|
All products and company names mentioned herein are
the trademarks of their respective owners. No part of this
website may be reproduced without the prior written permission
of Computer Books Online. Prices and availability subject to
change without notice..
|
|
|
|
|
|
