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.
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.