Metraipolis › archive › dc_167ddbf7892b
Anti-pattern — Wikipedia (en)
- Source
- Wikipedia (en)
- Original
- https://en.wikipedia.org/wiki/Anti-pattern
- License (as archived)
- CC-BY-SA-4.0
- Archived
- 2026-11-09T14:17:40.693Z
- SHA-256 of the archived text
cfeb4436c10dd67db78d57ea14251d68c0335373d17003a47beb9399668be4b4- Stable URL of this page
https://metraipolis.com/documento/dc_167ddbf7892b
How to cite
Anti-pattern — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Anti-pattern (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_167ddbf7892b (Metraipolis archive dc_167ddbf7892b, sha256 cfeb4436c10dd67db78d57ea14251d68c0335373d17003a47beb9399668be4b4)
BibTeX
@misc{dc167ddbf7892b,
title = {Anti-pattern — Wikipedia (en)},
howpublished = {Wikipedia (en)},
url = {https://en.wikipedia.org/wiki/Anti-pattern},
note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_167ddbf7892b; sha256 cfeb4436c10dd67db78d57ea14251d68c0335373d17003a47beb9399668be4b4},
year = {2026}
}Archived text
Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Anti-pattern. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
An anti-pattern is any common but counterproductive solution to some class of problem. The term, coined in 1995 by Andrew Koenig, was inspired by the book Design Patterns which highlights reliable and effective software development design patterns. Michael Ackroyd described anti-patterns in a paper presented at the 1996 Object World West Conference. The 1998 book AntiPatterns popularized the idea and extended its scope beyond software design to include software architecture and project management. Other authors have extended it further to encompass environmental, organizational, and cultural anti-patterns. An anti-pattern can be distinguished from a bad habit, bad practice, or bad idea by two traits. First, anti-patterns are commonly used processes, structures or patterns of action that initially appear to be appropriate and effective, but have greater drawbacks than benefits. Second, there is another way to solve the problem that is documented, repeatable, and effective where the anti-pattern is not. Similar to patterns, a "rule-of-three" applies: to be an anti-pattern it should have occurred at least three times. Documenting anti-patterns can help to analyze a problem space and to capture expert knowledge. While some anti-pattern descriptions merely document the consequences of the pattern, good anti-pattern documentation also provides alternatives ways to minimize harm. Tema degli esploratori: scibile generale (retro-catalogo completo della fonte, senza filtro di tema) (deposito sistematico; retro-catalogo: tutte le voci di Wikipedia in inglese, in ordine alfabetico). Fonte: Wikipedia in inglese, voce «Anti-pattern» — https://en.wikipedia.org/wiki/Anti-pattern Wikidata Q76438: «procedure o modi di fare usati durante il processo di sviluppo del software che, pur essendo lecitamente utilizzabili, si rivelano successivamente inadatti o controproduttivi nella pratica» (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q76438 Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Anti-pattern?action=history). Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza. Estratto dell'introduzione non modificato nel contenuto; revisione 1376517271, consultata il 2026-11-09T14:14:09.306Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: b3d756a103f65a62759714232a4e6c628b09964bd82fd1bffb2c1759e50c83c9