Anti-pattern

In computer science, anti-patterns are problems that happen frequently in computer programming and that should be avoided in good practice. In other words, while design patterns are good examples, anti-patterns are bad examples. They are also known as pitfalls.

Among them are:

• abstraction inversion
• accidental complexity
• action at a distance
• accumulate and fire
• ambiguous viewpoint
• analysis paralysis
• big ball of mud
• blind faith
• boat anchor
• busy spin
• caching failure
• checking type instead of membership
• code momentum
• code smell
• continuous obsolescence
• creeping featurism
• cut and paste programming
• dead end
• design by committee
• DLL hell
• Double-checked locking, in some situations.
• empty subclass failure
• God object
• input kluge
• interface bloat
• hardcodes are evil
• lava flow
• magic pushbutton
• mushroom management
• poltergeists
• premature optimization
• race condition
• reinventing the wheel
• smoke and mirrors
• software bloat
• spaghetti code
• stovepipe system
• vendor lock-in
• warm bodies

References

• Perl Design Patterns Book