If you don't vote, who will? Login and vote now.
By bloid
via blog.thinkrelevance.com
Published: Feb 23 2008 / 19:24
Design patterns are the enemy of agility. They introduce repetition and accidental variation to your codebase. Design patterns encourage you to create "point solutions" throughout your application, instead of cleanly isolating concerns. And they will make your code refactor-proof, no matter how cool your IDE is. But there is hope: Catch your design patterns while they are young, and teach them to be library calls instead.
Comments
bspies replied ago:
A ridiculous premise with an equally ridiculous conclusion. I don't see anything here disproving the value of any real pattern (Proxy, Decorator, etc.), but rather a trumped-up use case which he calls a design pattern because it fits the definition of a "pattern".
dzonelurker replied ago:
You sometimes need the parody to see the ridiculousness of a subject.
vidarh replied ago:
The real argument, which is badly formulated, is that re-opening a class and just using "def" to define a new method without providing some form of detection/avoidance of colliding method names is an anti-pattern _and_ that design patterns that can be implemented as a library call in your language should be rather than be reimplented all over.
The two arguments aren't really connected, and going from that to bashing design patterns is a pretty big stretch.
Voters For This Link (7)
Voters Against This Link (11)