Does it matter pattern? When multiple team members or even teams wasting lot of time arguing about stuff that don't even matter. Like spending 100 men hour in discussion about what the value of a string constant should be.
The framework pattern: usually very complex to use shared functionality that has basically no value behind it and it is being used because 'it is already there' or 'it is a standard way of doing something'. Very common in enterprise grade solutions where enterprise grade specialists need to justify they enterprise grade pay.
The framework consumer pattern: when someone uses framework without understating its base concept. Usual case might be usage of very complex framework with a bunch of dependencies to avoid writing 15 lines of code. It really goes well together with The framework patter in enterprise grade solutions where complete uselessness of the framework is amplified with complete dumbness of the user.
Stack overflow warrior: I think no explanation needed here =)
Hack amplification pattern (hacks snowballing into other groups/teams causing them to add hacks, which then causes further hacks, which then causes .... <and repeat>).
<new project>
by forking/starting off with a fork of OpenStack Nova (what could go wrong, what could go right?)