AntiPatterns

Brown, W. J., Malveau, R. C., III, H. W. M., & Mowbray, T. J. (1998). AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. Wiley.

Type

Book

Intellectual base

Textbook

Year

1998

Link

https://www.wiley.com/en-us/AntiPatterns%3A+Refactoring+Software%2C+Architectures%2C+and+Projects+in+Crisis-p-9780471197133

Cited from

architecture_urban_planning, cognitive_science, systems_cybernetics

Cited by

5 citations across 5 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Design Patterns
  • A pattern recognized as appropriate in one context is applied in another where it does not fit, producing overengineered, mis-optimized, or structurally incorrect design—the central concern of Brown, Malveau, McCormick, and Mowbray's (1998) AntiPatterns, which catalogues recurring mis-applications and refactored solutions.

    This sourceInverse pattern catalog documenting common mis-applications and refactored solutions.

• Law of the Instrument
  • Software architecture: the golden-hammer anti-pattern, where a team that has mastered microservices reads every requirement as a microservices decomposition while a monolith-comfortable team reads the same requirement as a monolith feature.

    This sourceDefines the 'Golden Hammer' anti-pattern — a team applies a familiar technology or framework to every problem regardless of fit.

• Retention Under Removal Uncertainty
  • In software codebases it is the lava flow: obsolete code retained because safe removal would require reading the whole call graph, running downstream tests at risk, and accepting blame for any breakage, while commenting-out is easy and deletion is hard.

Mechanisms

• Anti-Pattern Catalog
  • Its failure mode is anti-pattern zealotry: once every difficulty has a scary name, the catalog becomes a cynicism engine and every hard project gets branded a Big Ball of Mud
• Anti-Pattern Review
  • It is strongest in fields that have accumulated named failure modes masquerading as good solutions — software engineering's "anti-pattern" is the canonical case.

    This sourceThe mechanism generalizes the idea — a catalog of a pattern's look-alike failures — to any archetype.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://www.google.com/books/edition/AntiPatterns/Y6jpQG2WdvYC ×1

Registry ID ref:16a1c5571373 · see in the full table