As I see it, the main advantage of Design Patterns (whether they be a UX or Code pattern) over code or widget libraries, is that they are transferrable across programming languages and dev platforms.
Also, speaking only in the domaine of S/W Design patterns (as opposed to UX design patterns), many of the most useful patterns are things that simply cannot be wrapped into a standard library. You just have to understand the pattern, and how to implement it in your specific cases.
For example, I don't see how one could write a standard class for a pattern like factory method:
For sure, some patterns could be made into standard classes, but often I find that the "generic" implementation is harder to use and understand than a custom implementation. Often, you don't need all the bells and whistles of a pattern, and you are better off using the "Simplest Implementation That Could Possibly Work" for that pattern, in the context of your application.
] On Behalf Of Austin Govella
Sent: Thursday, January 26, 2012 7:35 PM
Subject: [agile-usability] Are design patterns an anti-pattern
We just published an article by Stephen Turbek on Boxes and Arrows
that argues against pattern libraries in favor of code libraries:
As someone who often promotes pattern libraries to aid rapid, usable
design for agile teams, I was struck by Stephen's analysis. And it
made me recognize that the "patterns" I've seen be most effective all
included widgets/code developers could just plug in.
So, two questions:
1. Do you agree? Pattern libraries are less useful than code libraries?
2. Are they only better for agile teams? (Are traditional pattern
libraries better for waterfall-driven organizations)?
Catch me at the IA Summit in New Orleans, Mar 23-25, presenting
"The miracle farmer's almanac":
Watch my presentation from Schiplcon 2011:
Listen to my presentation from SXSWi 2011:
Yahoo! Groups Links