[deviate_X]

In the real world being a good developer is not about programming ability. A great programmer needs to absolutely engage in managing perception in the everyday working environment.

The reasoning is if programmer A addresses issues 2X as fast as programmer B.

Then as things average out programmer A will generate 2X more issues than programmer B all else being equal.

Managers, clients and fellow programmers will almost always see programmer A as a problem and programmer B as a hero in this situation.

[projektir]

I don't agree with your choice of words here. A developer is absolutely about his technical ability combined with the people skills needed to use that ability within a team. That is, after all, the purpose of the specialization.

That a developer would benefit from other specific people skills doesn't mean those skills become part of being a great developer. A developer would also probably benefit from being more good looking due to human psychology, but what does that have to do with the profession itself?

Rather, this means that the industry favors politics over development, which is a problem with the industry. The fact that it is not great developers who will ultimately prosper in this environment should alarm you.

Perhaps that's the answer to the question of: "Where have all the good developers gone?" - nobody wants them.

[deviate_X]

I would argue that people feel "a developer is absolutely about his technical ability" but when you look at it you will find that this is a feeling rather than something which is in any way quantified as hinted at in article.

Very rarely does management decipher a developers problem solving skills, or rank the quality of code or rank eagerness to learn for example ..management does not do this.

What they do is judge "good team members" (and is that developer nice to me is very important) and "can they trust" which and goes back to "frequency of positive interactions" / "how often do you have do deal with issues".

[Nomentatus]

Good point, namely that doing less is the best way to avoid creating bugs. Which screws up many a metric. But you need scare quotes around "good developer."