The "pattern coder", applies design patterns the all parts of his code without really understanding why. His trust in authorities such as people that give tech

The "pattern coder", applies design patterns the all parts of his code without really understanding why. His trust in authorities such as people that give tech talks are the only reason needed to why his coding style is good. This person often ends up with very slow code that no one can modify or debug because his hello world function uses 200 sub-functions spread over 400 files. A common speech pattern of this archetype is "This is how you write stable/mantainable code". Edit: Just noticed it's only about "staff"-engineers. I wondered why there were only 4. However, i think the "solver" isnt part of the staff either.