Pattern Languages of Program Design¶
Coplien, J. O., & Schmidt, D. C. (1995). Pattern Languages of Program Design. Addison-Wesley.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Design Patterns
- Design Patterns overlap in naming and concept with related abstractions but operate distinctly. Archetype (see related entry #223) refers to universal symbolic figures in narrative and collective psychology (the Hero, the Shadow, the Mentor); archetypes transcend domains and carry psychological/mythic weight, whereas design patterns are practical engineering solutions in specific domains. Template refers to concrete starting code, form, or structure—a boilerplate you instantiate; patterns describe abstract design structures that can be implemented many ways and are not themselves code. Algorithm is a specific computational procedure with defined steps and complexity bounds; patterns are design structures that may organize algorithms but are not procedural instructions. Best practice is an observed good approach; a pattern formalizes the why (problem, context, consequences) behind the practice, a definitional distinction the Pattern Languages of Program Design community articulated through Coplien and Schmidt (1995).
This sourceFirst PLoPD volume from the PLoP conferences; establishes the pattern community's definitional standards distinguishing patterns from best practices, templates, and algorithms.
- Design Patterns overlap in naming and concept with related abstractions but operate distinctly. Archetype (see related entry #223) refers to universal symbolic figures in narrative and collective psychology (the Hero, the Shadow, the Mentor); archetypes transcend domains and carry psychological/mythic weight, whereas design patterns are practical engineering solutions in specific domains. Template refers to concrete starting code, form, or structure—a boilerplate you instantiate; patterns describe abstract design structures that can be implemented many ways and are not themselves code. Algorithm is a specific computational procedure with defined steps and complexity bounds; patterns are design structures that may organize algorithms but are not procedural instructions. Best practice is an observed good approach; a pattern formalizes the why (problem, context, consequences) behind the practice, a definitional distinction the Pattern Languages of Program Design community articulated through Coplien and Schmidt (1995).
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:1218e43ee295 · see in the full table