See this.

I love "The Premature Optimizer":

Never use String.IsNullOrEmpty! Didn't you know that there's a huge bug in the Framework that makes that function kill kittens if you call it on a multi-proc system with more than 4.5 gigs of RAM? Plus, it adds five microseconds of overhead as it accesses eax twice necessitating 4 extra clock cycles. Measure it? Should I have to, it's SO obvious that's inefficient!

When I write code, especially when alone, I imagine I am having a conversation with someone and trying to explain what I want the computer to do through code. It's like pair programming with an imaginary friend I call, "Future-Guy-That-Has-To-Maintain-This-Code." Not as good as real pair-programming, but whatever. 

When I read this, I remember thinking, "Crap! I've been saying String.IsNullOrEmpty is the bomb for a long time now, because it's so obvious and self-explanatory...now I am going to have to stop using it and explain why every freaking time! This sucks!" I recovered, but I think my imaginary pair-buddy that day must have been "The Premature Optimizer."

As to the labels/stereotypes thing: I think a better name for this would be "anti-pattern." These are all examples of people I _wouldn't_ want to work with, not personality types I hope the Visual Studio team wastes valuable time catering to, unless it's in the form of a cure or some kind of corrective treatment.