AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis

SLav said Highly recommended for all software engineers (and Project Managers). Highly recommended for all software engineers (and Project Managers). Some patterns won't apply, so don't feel like you'll have to read it straight through, but there are a lot of good patterns and solutions in here. I also like that they specifically call out when an Anti-Pattern might be the best solution for a particular problem. It is a little dated so some of their solutions have been replaced by better solutions in modern languages, but you can always take their examples and just port them to the la. Reality in front of us This book showed me the reality: problems in management and development. And then a solution appears to every problem. These problems repeat again and again over time. Sadly, we don't stop to review those problems, prefering to omit them than confront. Now, the book give us the description about problems explicity and the related solutions. And, in practice, it's very useful. Commonly observed, the Analysis Paralysis is an anti-pattern for large projects, and cause the major problems in management.The boo. "Off target for what I was after" according to Paul Edwards. I'd previously bought the Management Anti-patterns book, which is excellent. There were a couple of references to this book that intrigued me, so I followed up and got this one. The loss of one star is that I only found Off target for what I was after I'd previously bought the Management Anti-patterns book, which is excellent. There were a couple of references to this book that intrigued me, so I followed up and got this one. The loss of one star is that I only found 3-Off target for what I was after Paul Edwards I'd previously bought the Management Anti-patterns book, which is excellent. There were a couple of references to this book that intrigued me, so I followed up and got this one. The loss of one star is that I only found 3-4 of the described anti-patterns useful. The loss of the other star is that the taxonomy is weaker than the management one, so all of the anti-patterns cited in this book are less useful as a result.. of the described anti-patterns useful. The loss of the other star is that the taxonomy is weaker than the management one, so all of the anti-patterns cited in this book are less useful as a result.. -Off target for what I was after Paul Edwards I'd previously bought the Management Anti-patterns book, which is excellent. There were a couple of references to this book that intrigued me, so I followed up and got this one. The loss of one star is that I only found 3-4 of the described anti-patterns useful. The loss of the other star is that the taxonomy is weaker than the management one, so all of the anti-patterns cited in this book are less useful as a result.. of the described anti-patterns useful. The loss of the other star is that the taxonomy is weaker than the management one, so all of the anti-patterns cited in this book are less useful as a result.

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. 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. Luckily, they suggest ways to overcome antipatterns and improve software productivity in "refactored solutions" that can overcome some of these obstacles. The authors then proceed to define antipatterns oriented toward management problems with software (including Death by Planning and Project Misma

"The AntiPatterns authors have clearly been there and done that when it comes to managing software development efforts. * Over 80% of all software projects are deemed failures. * Two-thirds of all software projects encounter cost overruns in excess of 200%. 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. 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. Just look at the statistics: * Nearly one-third of all software projects are cancelled. I resonated with one insight after another, having witnessed too many wayward projects myself. The authors then show you how to detect and defuse AntiPatterns as well as supply refactored solutions for each AntiPattern presented.. 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. 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