Well, the stereotype I was shooting for was someone who overarchitects things and who is really shackled to some particular set of concepts, methodologies, and tools; the sort of person who will go on implementing "factories" and "strategies" in languages and situations where they don't apply.

Personally, if I were tasked to explain that distinction, I would shorten (1) to "a good programmer" and shorten (2) to "a bad programmer."