Anti Patterns Catalog
c2.com
c2.com
You can also try reading the anti-patterns book for an introduction to many of the most important ones, or rather books: http://www.amazon.com/s?index=blended&link_code=qs&f...
Although I can only vouch for the tremendous usefullness of the first: http://www.amazon.com/AntiPatterns-Refactoring-Software-Arch...
Hmmm, I think it went out of print but it's back.
I'd also like to see design/programming patterns distinguished from organizational patterns like Empire Building or Hero Culture (though not surprisingly, they tend to be correlated with each other.)
Regarding the commonality of these patterns, having worked in an Oracle environment for a while, the ones I see most often seem to be Stovepipe systems and Big Ball of Mud. SQL in particular tends to force a stovepipe approach, because if you try to hide too much complexity behind nice PL/SQL interfaces, you tend to get highly suboptimal explain plans, and/or, you end up losing advantages of multi-block I/O and batch processing. So, instead, you have huge multi-table joins that are inherently brittle and difficult to maintain but which perform adequately. (Yes, views can help here to some degree.)
Because you don't have many clean interfaces, refactoring becomes more difficult and you also get tons of copy/paste code, resulting in an eventual Big Ball of Mud.
It's also worth noting that greenfields projects tend to be rare in our field, more often you're starting with an existing brownfield code base. GoF addresses the former, anti-patterns directly address the latter, although it's of course useful to know about anti-patterns so that you can avoid falling into them when you've got a greenfield to start with.