Anti-Pattern
A common response to a recurring problem that is usually ineffective and risks being highly counterproductive.
EverydayConcepts.io
Origin
Software engineer Andrew Koenig coined the term in the March–April 1995 edition of the Journal of Object-Oriented Programming, defining it as "just like a pattern, except that instead of a solution it gives something that looks superficially like a solution, but isn't one." Inspired by the Design Patterns book, Koenig's coinage identified common ineffective responses to recurring problems. Michael Ackroyd presented a paper on anti-patterns at the 1996 Object World West Conference, and the 1998 book AntiPatterns popularized the term beyond software design.
Updated February 22, 2026