When did this anti-Design-Patterns meme start, again? Was it the most recent Yegge novel, or was it earlier than that?
I'm not completely sure what raganwald is saying, but I think he's saying this: knee-jerk opposition to the use of Design Patterns is just as silly as knee-jerk opposition to most any other technology.
Part of the job of a good developer is to sort out the BS from the hype, from the long-term, useful information. And for better or worse, Design Patterns (just like Java and C++ and other things that have survived long enough that they are no longer flavor-of-the-moment fads) reflect real-world needs, or they simply wouldn't be as well-known and widely used as they are.
Said another way: the problem isn't Design Patterns; the problem is the bad developers who don't know how to use Design Patterns.
I write programs with Design Patterns, I catalogue new ones from my work, I use them to teach and communicate. "A Pattern Language" is one of my favourite books.
What did I say? Well, I quoted someone else telling a story about their experience:
I thought it was a good story because it illustrated two different mind sets when it comes to writing programs and what happens when they come into contact with each other. There's no preachy conclusion, it's a human interest story.
I also talked about a particular cultural approach in this post:
As I said, I wasn't totally clear on your intent, so I hope you don't take my comment personally. It seems that we agree, in most ways.
The anti-DP meme is just a trend that I have been detecting in the threads here, and in other places. I was commenting on a phenomenon that is bigger than you (but to which you /do/ seem to be responding).
Almost all 'design patterns' are just instances of yet another pattern: The Human Compiler.
Make your language do something it can't naturally do, by having to transform abstractions into hand crafted code. Especially when using a higher level language would make that 'design pattern' automatic or innecesary.
That said, I'm not agains patterns per se, I just don't see them as the 'Holy grail' that fixes all the developer problems if only you used them well, because they are nothing of that sort.
'Design patterns' are simply like an Assembler programmer doing ADTs, just because he knows about OOP, and he is methodic about his work, but it doesn't mean that what he's doing is the only way to use classes when programming.
5 comments
[ 2.6 ms ] story [ 28.5 ms ] threadI'm not completely sure what raganwald is saying, but I think he's saying this: knee-jerk opposition to the use of Design Patterns is just as silly as knee-jerk opposition to most any other technology.
Part of the job of a good developer is to sort out the BS from the hype, from the long-term, useful information. And for better or worse, Design Patterns (just like Java and C++ and other things that have survived long enough that they are no longer flavor-of-the-moment fads) reflect real-world needs, or they simply wouldn't be as well-known and widely used as they are.
Said another way: the problem isn't Design Patterns; the problem is the bad developers who don't know how to use Design Patterns.
I write programs with Design Patterns, I catalogue new ones from my work, I use them to teach and communicate. "A Pattern Language" is one of my favourite books.
What did I say? Well, I quoted someone else telling a story about their experience:
http://weblog.raganwald.com/2007/12/newly-discovered-design-...
I thought it was a good story because it illustrated two different mind sets when it comes to writing programs and what happens when they come into contact with each other. There's no preachy conclusion, it's a human interest story.
I also talked about a particular cultural approach in this post:
http://weblog.raganwald.com/2007/12/pouring-water-back-into-...
There, I expressed opposition to the idea of a fixed set of standard patterns.
So, now you know what I was saying.
The anti-DP meme is just a trend that I have been detecting in the threads here, and in other places. I was commenting on a phenomenon that is bigger than you (but to which you /do/ seem to be responding).
Thanks.
Make your language do something it can't naturally do, by having to transform abstractions into hand crafted code. Especially when using a higher level language would make that 'design pattern' automatic or innecesary.
That said, I'm not agains patterns per se, I just don't see them as the 'Holy grail' that fixes all the developer problems if only you used them well, because they are nothing of that sort.
'Design patterns' are simply like an Assembler programmer doing ADTs, just because he knows about OOP, and he is methodic about his work, but it doesn't mean that what he's doing is the only way to use classes when programming.