AntiPatterns¶

Brown, W. J., Malveau, R. C., McCormick III, H. W., & 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¶

6 citations across 6 artifacts.

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

Primes¶

Design Patterns
- Formal/abstract: In software, the Singleton pattern (ensuring a class has exactly one instance) was canonical in Gamma et al. (1994) when global state was common.
  This sourceInverse pattern catalog documenting common mis-applications and refactored solutions.
  
  Supported in partVerified against the work's full text
  
  Wiley's product page confirms AntiPatterns catalogues AntiPatterns with refactored solutions, but it is publisher copy and never states the cross-context mis-application mechanism the claim calls the book's central concern.
  
  “The authors then show you how to detect and defuse AntiPatterns as well as supply refactored solutions for each AntiPattern presented.”
  From the work's full text.
  
  Read by an automated reader; not a human review. How support was checked
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.

Domain-specific¶

Golden Hammer Anti-Pattern
- The golden hammer anti-pattern (Brown et al., AntiPatterns, 1998)
  This sourceThe book that names the Golden Hammer AntiPattern, a familiar technology or concept applied obsessively to many software problems.
  
  SupportedVerified against the source
  
  Read by an automated reader; not a human review. How support was checked

Mechanisms¶

Anti-Pattern Catalog
- An Anti-Pattern Catalog indexes recurring structures that look like reasonable choices but reliably produce bad outcomes — each entry a named trap paired with the remediation that gets you out of it.
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 sourceCatalogues named, recurring software-development, architecture, and project-management practices that appear useful but lead to harmful results.

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? Read against the text for 2 of 6 citations: 1 supported, 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.

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.

Links previously used in the corpus¶

Before the registry existed this work was also linked 2 other ways.

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