5 ms·
Reading that list one thing kept popping into my head.... design patterns.
by austincheney 10y ago
Reading that list one thing kept popping into my head.... design patterns.
- olavk 10y agoDesign patterns are tools. Don't use a hammer if you don't need a hammer, you will just destroy something. And vice versa: Don't eschew the use of a hammer when you actually need it, just because you once saw some guy use a hammer in an inappropriate context.
- mceachen 10y agoCertainly. But I think people read the TL;DR: as "oh, design patterns are bad" or "don't use the wrong tool for a job." A better TL;DR is a bit more nuanced: Broad familiarity with your tools and their applicability (design patterns or otherwise), is a prerequisite to picking a reasonable tool for a given task.
- segmondy 10y agoIf you think there is something wrong with design patterns, then you still have a lot to learn. Improper use of design patterns is a thing and this I can agree with, sadly, from what I've seen, design patterns are rarely used. People tend to stumble unto them and implement them poorly at best.
- kedean 10y agoHonestly, I think overuse has become it's own problem. Design patterns are not a suggestion, you shouldn't strive to use them. Devs shouldn't start a project and think 'what design patterns will I use here'. They exist so that you can identify what you are already doing and avoid past mistakes that others have already made (hell, the GoF book states this in the intro). Nobody should go into a project thinking 'I will use the singleton pattern for this', but if halfway in you realize that your system fits that pattern, it's there for you.