Patterns!
-
I had this argument while I was still in college. A team member had decided the entire major was worthless because we had to use prescribed solutions to everything. Apparently having missed the point that these general solutions can (and should be) modified to fit a situation, and the point of our major was identifying when a pattern would be useful and exactly how to implement it in that situation to best benefit the software and our own sanity. I mean hell, look at adaptor. It's a stopgap solution to keep you from having to re-write libraries and nothing more. This isn't a sacred text it's a few useful ideas. But yeah, doesn't stop people from treating it like their personal bible.
Thou shalt follow the hallowed word of the holy pattern! ;P
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
It's as old as Methuselah! Or almost! Voodoo programming[^]
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
I thought it was "cargo cult programming".
You'll never get very far if all you do is follow instructions.
-
B413 wrote:
or me there is an incompatibility between "pattern" and "Agility" because when you are Agile your architecture emerge
This sounds like the classic misunderstanding of agile that goes roughly along the lines of 'since things change, we never need to design'. I work mostly on agile projects and I can tell you that design patterns are very important to make sure you develop in a way which can accommodate that change. If anything, getting a good framework design is more important in agile because it strongly affects your ability to adapt during development, and that's the essence of agile.
BobJanova wrote:
This sounds like the classic misunderstanding of agile that goes roughly along the lines of 'since things change, we never need to design'.
Agility (and Scrum) pretend architecture emerge. I also work mostly on agile projects and I'm agree that design is very important to make sure you develop in a way which can accommodate that change but design patterns are not the only way to design something. I remember the time I had to argue against patterns that now are become anti pattern. And that the problem with patterns. When a pattern is not correct it's hard to argue against it because every book, every web page defend it until he became an anti pattern years latter... It is why I think it is more important to know its anti patterns. And I'm not talking about teams that don't really understand to goal of a pattern and that incorrectly implement it. And some patterns are so complex they don't respect the Keep It Simple and Stupid rule.