Revision as of 16:24, 27 August 2025 edit Stevebroshar (talk \| contribs) Extended confirmed users 5,253 edits Remove structure since doesn't add value; not enough content for all that structure ← Previous edit		Latest revision as of 16:28, 27 August 2025 edit undo Stevebroshar (talk \| contribs) Extended confirmed users 5,253 edits mNo edit summary
Line 1: {{Short description \|Solution to a problem that may be commonly used but is generally a bad choice}} An '''anti-pattern''' is a solution to a class of problem that although may be commonly used, is likely to be ineffective or counterproductive.{{sfn\|Budgen\|2003\|p=225}}{{sfn\|Ambler\|1998\|p=4}} The term, coined in 1995 by [[Andrew Koenig (programmer)\|Andrew Koenig]], was inspired by the book ''[[Design Patterns]]'' which highlights [[software development]] [[design pattern]]s that its authors consider to be reliable and effective.{{sfn\|Neill\|Laplante\|DeFranco\|2011\|p=4}} A ~~further~~ paper in 1996 presented by Michael Ackroyd at the Object World West Conference described anti-patterns.{{sfn\|Neill\|Laplante\|DeFranco\|2011\|p=4}} It was, however, the 1998 book ''[[AntiPatterns]]'' that both popularized the idea and extended its scope beyond the field of software design to include software architecture and project management.{{sfn\|Neill\|Laplante\|DeFranco\|2011\|p=4}} Other authors have extended it further since to encompass environmental, organizational, and cultural anti-patterns.{{sfn\|Neill\|Laplante\|DeFranco\|2011\|p=5}}

Anti-pattern: Difference between revisions