Eduardo Menard flag Denunciar. Brown Raphael C. Malveau Hays W. Brown, Raphael C. Malveau, Hays W. All rights reserved.
|Published (Last):||1 March 2007|
|PDF File Size:||5.3 Mb|
|ePub File Size:||17.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book. Refresh and try again.
Open Preview See a Problem? Details if other :. Thanks for telling us about the problem. Return to Book Page. Preview — Antipatterns by William J. Brown Contributor ,. Raphael C.
Hays W. 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 a team of object-oriented systems developers, AntiPatterns identifies 40 of the most common A 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 a 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.
Get A Copy. Paperback , pages. More Details Original Title. Other Editions 3. Friend Reviews. To see what your friends thought of this book, please sign up. To ask other readers questions about Antipatterns , please sign up. Lists with This Book. Community Reviews. Showing Average rating 3. Rating details. More filters. Sort order. May 30, Erika RS rated it did not like it Shelves: software , formerly-owned. It saddens me to say so, but this book deserves that score.
AntiPatterns has an excellent premise: just as there are good patterns which benefit the development process, there are also bad patterns. These negative patterns can be at many levels including the level of code, the level of architecture, and the social level. As anyone who has been on a real project knows, there is plenty of material for a book wi 1 out of 5 is the score I reserve for books that I consider a waste of my reading time.
As anyone who has been on a real project knows, there is plenty of material for a book with this premise. Sadly, despite the occasional glimmer of interest, this book does not deliver on that potential. Rather, it is dated, boring, and vague. Another historical artifact, at least relative to software development at my workplace, is the strict division of architects and developers.
Developers, it seems, are naught but the lowly dregs, necessary only because architects cannot dirty their hands with the writing of actual code. In addition to being annoying, this division is unrealistic.
In my world, you need both sets of skills, and I believe, from personal and collected anecdote, that those with both perspectives will come to better solutions. I could forgive the dated references and social structure if the book were otherwise interesting. I quite enjoyed The Mythical Man-Month despite its age.
However, this book was boring. The authors used a distinctly academic style. As a reader, I don't care about the general development of the field of software patterns. I don't care to read in excessive detail about who else may have named a similar antipattern or why the authors think their version is better. I want substance. And yet, substance rarely appeared.
Comically, although perhaps understandably given how definitions drift over time, the authors called the solutions to their antipatterns the "Refactored Solution". But the solutions were generally vague and unactionable. For example, one antipattern is "The Blob", that class that does everything and is the heart of your application yup, I'm familiar with that one. The suggested solution: find cohesive components, move them into other places if such places exist, otherwise create such places.
You're done. As if it's that simple. The coupling within real blobs is deep; without a description of how to manage that complexity, the refactored solution does not go beyond common sense. The other antipatterns follow this same pattern: a description of a very real problem is followed by a worthless solution. I did get something out of this book: as with traditional design patterns, one of the best things about anti-patterns is that they name common problems, making them easier to talk about.
That said, the 6 page appendix which summarizes all the patterns provides all of that value. As for the rest of the book, it was a waste of time. Dec 01, Charles rated it it was amazing. How to avoid a rut in software development In , a book was published that caused a mini-revolution in the field of software development. Their approach was to describe software in terms of patterns, which are abstractions that are more general than a standard algorithm.
Since that time, a small but growing band of individuals have made great progress in the codification and application of patterns. Preliminary indications are that properly under How to avoid a rut in software development In , a book was published that caused a mini-revolution in the field of software development. Preliminary indications are that properly understood, and it is problematic that anyone really does at this time, and applied patterns will have a substantial affect on software development.
An antipattern is a pattern that has negative consequences when applied. This ranges from the antipattern that almost always leads to a negative consequence to those that are generally positive, but lead to negative results when used in the wrong context.
One example is the Cut-and Paste Programming antipattern. We all have benefited from the use of cut and paste and we have all suffered when we used it in an inappropriate situation. Many such examples are given, and fortunately for us all, for each antipattern the authors provide instructions on how to recognize it, what causes it and how to cure it.
Anyone who has worked in software development has experienced one or more of these problems. In keeping with a negative often being more significant than a positive, it is quite possible that the study of antipatterns will yield more substantial results than similar effort being expended elsewhere.
Dec 11, Billy Dean rated it it was ok. Am I missing something? Was there a contest to see how often someone could repeat the word, "AntiPatterns" on a single page, in a single paragraph, in a single sentence? If you're not already familiar with the concept of antipatterns, it'll be a while in this book before you get a straight answer as to what an antipattern is.
If you're already familiar with the concept, then you probably don't need this book to begin with. It's packaged as a revolutionary idea, but a couple brief paragraphs woul Am I missing something? It's packaged as a revolutionary idea, but a couple brief paragraphs would be enough to explain what it is and how to apply it. Skim this book for what you need and move on. Oct 09, Adam rated it liked it Shelves: technical.
Some interesting ideas in this book, but only about 60 pages of real content, stretched to fill their quota. Worth reading, but get a used copy and skim the portions where the author is rambling. A much better read with a similar topic is "The Pragmatic Programmer". Nov 22, Sepehr rated it did not like it. There are refactoring classics you should consider instead.
Sep 05, Foxtrot Romeo rated it liked it Shelves: technical-readings. The content could have been summarized in a few dozens of pages. And the core concepts definitely fit in 5 pages. Feb 16, James rated it really liked it Recommends it for: Coders.
Shelves: diy , non-fiction. Since many of the problems in this book are focused on behavior, it's still mostly useful. It has a bit of a negative feel, it concentrates solely on problems.
Antipatterns: Refactoring Software, Architectures, and Projects in Crisis
You are currently using the site but have requested a page in the site. Would you like to change to the site? William J. Brown , Raphael C. Malveau , Hays W. Request permission to reuse content from this site. Undetected location.
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions.
Wiley - AntiPatterns, Refactoring Software, Architectures, and Projects in Crisis
Skip to search form Skip to main content You are currently offline. Some features of the site may not work correctly. Malveau and Hays W. McCormick and Thomas J. Mowbray Published Engineering. 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.
Welcome to the Hot Best sellers, Gain insight and understanding as you learn from this very entertaining book exactly how to recognize and then master your Software Development troubles You always knew you'd laugh at your CM troubles someday! This web site is all about AntiPatterns. Wiley and Sons. We set out here to provide as complete a picture as we can about just what an AntiPattern is, why it's important and what we can and should be doing about them. It's been a long time since we made any updates to this site, and the original five AntiPatterns authors have long since gone our separate ways, although we do try to keep in touch as best as possible. However, we are very pleased to see that our books are being followed up by several more on the subject.