3 ms·
> What does design patterns provide on top of that? Only additional complexity and redundancy. understanding each other would be impossible if we just said, e.
by jcelerier 6y ago
> What does design patterns provide on top of that? Only additional complexity and redundancy.
understanding each other would be impossible if we just said, e.g. strategy or command.
"we use a strategy" can mean a ton of stuff in the context of a chat between developers in a company. "we use the strategy pattern" will be clear to everyone.
- neonological 6y agoChange the name strategy to something more clear. Kind of pretentious to use a common word "strategy" to describe a specific technique as if it's the most strategic pattern ever. It's like if someone came up with the "Logic pattern" or "Intelligence pattern."
- jcelerier 6y ago> Change the name strategy to something more clear. Kind of pretentious to use a common word "strategy" to describe a specific technique as if it's the most strategic pattern ever. It really makes sense though. I sometimes gave OOP classes to beginner students by having them discover the patterns on their own. Not only they manage to do that easily most of the time, but some of them also manage to give them the correct name, without any prior exposure to the GoF book.
- neonological 6y agoI disagree. Stuff like "Dependency injection" or "Inversion of control" are by far the most inflated names for such simple techniques. These names were deliberately chosen to inflate academic worth at the expense of clarity.