Learning JavaScript Design Patterns

Chapter 3. “Pattern”-ity Testing, Proto-Patterns, and the Rule of Three

Remember that not every algorithm, best practice, or solution represents what might be considered a complete pattern. There may be a few key ingredients here that are missing, and the pattern community is generally wary of something claiming to be one unless it has been heavily vetted. Even if something is presented to us that appears to meet the criteria for a pattern, it should not be considered one until it has undergone suitable periods of scrutiny and testing by others.

Looking back upon the work by Alexander once more, he claims that a pattern should be both a process and a “thing.” This definition is obtuse on purpose, as he follows by saying that the process should create the “thing.” This is a reason why patterns generally focus on addressing a visually identifiable structure—i.e., we should be able to visually depict the structure that results from the pattern in practice.

In studying design patterns, it’s not irregular to come across the term “proto-pattern”: a pattern that has not yet been known to pass the “pattern”-ity tests. Proto-patterns may result from the work of someone who has established a particular solution that is worthy of sharing with the community, but has not yet been vetted heavily due to its very young age.

Alternatively, the individual(s) sharing the pattern may not have the time or interest of going through the “pattern”-ity process and might release a short description of their ...