By Ultan O'Broin-Oracle on Jul 31, 2012
When user experience (UX) professionals talk about design patterns, it's wise to nuance the term, and qualify it. These patterns are proven, usability best practices and solutions for common problems. When developers talk about design patterns, they're referring to software development architecture or coding patterns based on frameworks or languages, and implemented through their development environment.
In the Oracle Application Development Framework (ADF) world, we have to contend with lots of patterns, starting with the underlying Model View Controller (or MVC) pattern, Java Enterprise Edition patterns for ADF Business Components, and lots of others that ADF developers use daily to make life easier. Check the ADF Enterprise Methodology Group (ADF EMG) Google Group forum and Oracle ADF Code Corner for some great insights into what code design patterns are used, how, and why.
And then, of course, we have that antipattern business to contend with, too!
So, dev outreach folks, know your audience and adopt terminology and messaging appropriately upfront. Otherwise, be prepared to spend some time in the translation business or answering questions about code.
Personally, I think usability best practices and guidelines for developers works well. However, when we do refer to design patterns in the UX sense, then we need to make sure the context is clear and qualify the term.