> People always say this, but it's not true in practice. It is true in practice, try talking to programmers who don't know about design patterns and you'll fin

> People always say this, but it's not true in practice. It is true in practice, try talking to programmers who don't know about design patterns and you'll find communication about architecture difficult. Maybe you haven't met enough of these programmers, but there's a shit ton of them in the corporate world. > If there isn't a term for something, you just make one and say what you mean by it. That's what we've always done and it's what programmers not under the influence of "design patterns" always still do. Yes, and it doesn't work well when you don't have a common vocabulary; you spend all your time trying to grok their little custom names for everything. Everything else you said is what happens when people mis-apply patterns and think they're code templates, they're not and were never intended to be.