33 ms·
I agree. The intended use as a shared vocabulary of precise terms of art never caught on, even though the names are good evocative names that people continue to
by dkarl 7y ago
I agree. The intended use as a shared vocabulary of precise terms of art never caught on, even though the names are good evocative names that people continue to use when talking about code. I haven't noticed any drop-off in programmers' ability to solve the underlying problems despite design patterns fading from near-compulsory for "any good programmer" to being a historical relic. Likewise, I haven't noticed that programmers communicate any less efficiently today even though it is no longer standard to review the design patterns terminology before every interview.
Applying design patterns to code seemed like a brilliant idea, but for some reason it wasn't a good fit for how people actually work and communicate.
- QueensGambit 7y agoMay be, most of the complex code is abstracted in libraries and frameworks these days. So, the design patterns may not be that useful in application code. But back in the days, when I was writing infrastructure code (Server/ORM), design patterns were super important. Without that, I wouldn't have understand any of the code written by my counterpart.