Wednesday, 28 March 2012

Anti-pattern

In software engineering, an anti-pattern (or antipattern) is a arrangement that may be frequently acclimated but is abortive and/or counterproductive in practice.12

The appellation was coined in 1995 by Andrew Koenig,3 aggressive by Gang of Four's book Architecture Patterns, which developed the abstraction of architecture patterns in the software field. The appellation was broadly affected three years after by the book AntiPatterns, which continued the use of the appellation above the acreage of software architecture and into accepted amusing interaction. According to the authors of the latter, there accept to be at atomic two key elements present to formally analyze an absolute anti-pattern from a simple bad habit, bad practice, or bad idea:

Some again arrangement of action, action or anatomy that initially appears to be beneficial, but ultimately produces added bad after-effects than benign results, and

A refactored band-aid exists that is acutely documented, accurate in absolute convenance and repeatable.

Many anti-pattern account bulk to little added than mistakes, rants, baffling problems, or bad practices to be abhorred if possible. Sometimes alleged pitfalls or aphotic patterns, this breezy use of the appellation has appear to accredit to classes of frequently reinvented bad solutions to problems. Thus, abounding applicant anti-patterns beneath agitation would not be formally advised anti-patterns.

By formally anecdotic again mistakes, one can admit the armament that advance to their alliteration and apprentice how others accept refactored themselves out of these torn patterns.

No comments:

Post a Comment