Patterns as an Anti-Pattern?



Email    print   
January 15, 2008 —  (Page 1 of 3)
For reasons that elude me, the arrival of the book “Design Patterns” in 1995 created enormous interest in the programming industry. The book, now known affectionately as the Gang of Four (or GoF) book due to its having four authors, posited a notion that did not seem radical, but which impressed a lot of people—namely, that there were recurring types of programming problems that could be addressed using a systematic sequence of steps.

That sequence of remedial activities was spelled out by the GoF, and these recipes—or patterns—became the object of considerable study. Exponents, such as former SD Times columnist Allen Holub, went on to say that all 23 GoF patterns should be learned, memorized and used by developers. The goal was that at various points in programs you could refer to the pattern and later developers would know from the name what the code did and how. So, for example, if you described a class as a Fa?ade, everyone would know that class was a front-end to some other subsystem.

I like this vision. In pure programming terms, the closest equivalent is collections. When I say that something is implemented as a hash table, you nod knowingly and you don’t need to check out the details of how data items are stored. Unfortunately, the patterns presented by the GoF never obtained the universal implementation that was required for this vision to succeed. Moreover, it turns out the patterns had numerous aspects that are questionable or not terribly helpful. Yet the static perception of their enduring value continues on.

First, let’s clarify that what we are talking about are not really design patterns. They are better described as implementation patterns. They are code-level solutions that help you implement a specific action. They are not the domain of architects and designers, but rather recipes for coders who implement designs. GoF patterns are much closer to the concept of refactoring and coding shortcuts than they are to techniques an architect would use in designing a project.




Pages 1 2 3 


Share this link: http://sdt.bz/31612
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Information Integration Patterns
I’ve been thinking about the patterns of information integration that we see these days, as related to SOA, in products Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb