Antipatterns in Software Architecture

This is a repost from my technology trends blog here

I have been putting together solutions in IT enterprise space for quite a while now. Some of the frameworks used over the years, for example are

• 4+1
• TOGAF (Recently started looking at it)
  
• Zachman framework

While TOGAF is a really a promising and an Agile way of doing things, I need to get more handle on this though.
One of the things, which amazes me while designing a solution or replying to an RFP, is heavy use of architectural and deign patterns. Using Patterns is not bad, but over the years i have found sometimes a simple solution become quit complex and bloated. I have burned my fingers in the past with this and have stared using some antipatterns approach as well. For those who are interested, I'm linking some of the architectural antipatterns here, I do refer them from time to time for my solutions.

• ArchitectureAsRequirements
• ArchitectureByImplication
• AutogeneratedStovepipeAntiPattern
• CoverYourAssets
• DesignByCommittee
• DoerAndKnower
• ExceptionFunnel
• FloatingPointCurrency
• FloatingPointFractions
• IntellectualViolence
• ImplementationInheritance
• ReinventTheWheel
• RollYourOwnDatabase
• SpaghettiCode
• StovepipeSystem
• SumoMarriage
• SwissArmyKnife
• TheGrandOldDukeOfYork
• VendorLockIn
• WarmBodies
• WolfTicket

What do you guys do, any thoughts?