: AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
|
|
In association with Amazon.com
|
by: William J. Brown, Raphael C. Malveau, Hays W. "Skip" McCormick, Thomas J. Mowbray
List Price: $49.99Amazon.com's Price: $39.99 You Save: $10.00 (20%)Prices subject to change. Availability: Usually ships in 24 hours
Binding: Kindle Edition
Dewey Decimal Number: 005.1
Format: Kindle Book
Label: Wiley
Manufacturer: Wiley
Number Of Items: 1
Number Of Pages: 336
Publication Date: April 03, 1998
Publisher: Wiley
Sales Rank: 29458
Studio: Wiley
Related Items:
Editorial Review:
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 800f 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.
Amazon.com:
If patterns are good ideas that can be re-applied to new situations, AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis looks at what goes wrong in software development, time and time again. This entertaining and often enlightening text defines what seasoned developers have long suspected: despite advances in software engineering, most software projects still fail to meet expectations--and about a third are cancelled altogether.
The authors of AntiPatterns draw on extensive industry experience, their own and others, to help define what's wrong with software development today. They outline reasons why problem patterns develop (such as sloth, avarice, and greed) and proceed to outline several dozen patterns that can give you headaches or worse.
Their deadliest hit list begins with the Blob, where one object does most of the work in a project, and Continuous Obsolescence, where technology changes so quickly that developers can't keep up. Some of the more entertaining antipatterns include the Poltergeist (where do-nothing classes add unnecessary overhead), the Boat Anchor (a white elephant piece of hardware or software bought at great cost) and the Golden Hammer (a single technology that is used for every conceivable programming problem). The authors then proceed to define antipatterns oriented toward management problems with software (including Death by Planning and Project Mismanagement, along with several miniature antipatterns, that help define why so many software projects are late and overbudget).
The authors use several big vendors' technologies as examples of today's antipatterns. Luckily, they suggest ways to overcome antipatterns and improve software productivity in 'refactored solutions' that can overcome some of these obstacles. However, this is a realistic book, a mix of 'Dilbert' and software engineering. A clever antidote to getting too optimistic about software development, AntiPatterns should be required reading for any manager facing a large-scale development project. --Richard Dragan
Customer Reviews
Average Rating: 
Rating:  - lots of good stuff
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", ... Read More
Rating: - worth a read
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.
Rating:  - helps to improve situation in software projects
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 ... Read More
Rating: - The dark side of software development
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 ... Read More
Rating:  - And the next thing you know your momma is a pattern
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, ... Read More
|
|
|
