Difference between revisions of "Anti-pattern"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (Created page with "An '''anti-pattern''' is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive. == Description == The term, coined in...") |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 13: | Line 13: | ||
* [[Design Smell]] | * [[Design Smell]] | ||
* [[List of software development philosophies]] – approaches, styles, maxims and philosophies for software development | * [[List of software development philosophies]] – approaches, styles, maxims and philosophies for software development | ||
| + | * [[Software design pattern]] | ||
* [[Software Peter principle]] | * [[Software Peter principle]] | ||
* [[Capability Immaturity Model]] | * [[Capability Immaturity Model]] | ||
Latest revision as of 07:31, 7 September 2016
An anti-pattern is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive.
Description
The term, coined in 1995 by Andrew Koenig, was inspired by a book, Design Patterns, which highlights a number of design patterns in software development that its authors considered to be highly reliable and effective.
The term was popularized three years later by the book AntiPatterns, which extended its use beyond the field of software design to refer informally to any commonly reinvented but bad solution to a problem. Examples include analysis paralysis, cargo cult programming, death march, groupthink and vendor lock-in.
See also
- Code smell – symptom of unsound programming
- Design pattern
- Design Smell
- List of software development philosophies – approaches, styles, maxims and philosophies for software development
- Software design pattern
- Software Peter principle
- Capability Immaturity Model
- ISO 29110: Software Life Cycle Profiles and Guidelines for Very Small Entities (VSEs)
External links
- Anti-pattern @ Wikipedia
