Coined by Andrew Koenig in 1995, anti-patterns are the ineffective opposite of reliable design patterns. Two factors that must be present to define the common response (or solution) as an anti-pattern, rather than a bad idea or habit.

These are:

• The course of action appears helpful initially, but typically generates more negative outcomes than positive

• There is another solution that has been documented and validated as more effective

Anti-patterns can occur from lack of knowledge (or experience) with solving a problem, or little awareness of other solutions. Others are caused by applying a good design pattern to an incompatible issue.

Common anti-patterns include:

1. Bicycle shed

   Reassigning resources to solve trivial issues.
   

2. Bleeding edge:

   Using new technologies that are not proven, which cause cost increases, performance issues, and/or delays.
   
   

3. Design by committee:

   Involving too many contributors in a design process, without a unifying vision.
   
   

4. Scope creep:

   Unregulated changes or adding new features to a project, after the original key requirements have been agreed.