pull down to refresh

Patterns have certainly mattered historically. Closures, interfaces, and first-class functions haven’t always existed in mainstream languages. Many patterns were non-obvious back then, and so it’s not a surprise that they emerged. But even Java itself, the language so terrible at fostering good architecture, it has become a joke, has had all of those feature for at least 10 years. So can we abolish “command” and “strategy” now, pretty please?

It’s certainly useful to know about the commonly utilized patterns, but experience with real code and a little agility will quickly get you up to speed regardless of how much time you’ve invested in studying patterns in theory, as long as you know the basic concepts. They’re good as a temporary mnemonic for newbies, not as must-know terminology.