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

Reference

\n* Perl Design Patterns Book