Whats in a (Pattern) Name?
Names are important because they are a key part of how we communicate. Names are labels we attach to concepts. Good names help us communicate the concepts. This is true both for when communicating with people who already know the names and especially for those who don’t. Let me illustrate this with an example. Early in my pattern-writing days, I attended the very first Pattern Languages of Programs (PLoP) conference. (http://www.hillside.net/conferences/plop)Well known author Jim Coplien (referred to as “Cope” by all his friends) had a pattern language of organizational patterns being workshopped. One of the patterns was called “Buffalo Mountain” and another was called “Architect Also Implements”. These two pattern names are at opposite ends of the spectrum as far as pattern names are concerned. The gist of “Architect Also Implements” can be gleaned from the pattern name by even those who have not read the pattern. The name is both a placeholder for the pattern and meaningful in its ow
