Maybe the first guy is just pissed that he has to put up with so much shit written by the second guy and is vocalising his desire to be free from it.
I prefer to think in terms of 'mean change turnaround' time; how quickly can your organisation or individual go from a problem or change request to functioning production system? If nothing ever breaks but new reports take 6 months, that's probably worse for business than the occasional outage and new reports taking 2 weeks.
It's a manager's responsibility to balance this out - but my point was SOMETIMES there's shit work - it's just unavoidable, and someone has to do it. And at that stage, there are people who do it, and people who don't ...
However, there really is no good way to do this, other than to hire somebody for a trial period and have them do actual real world tasks. That's what I try to do most of the time, but unfortunately it's not always possible. If someone has better ideas, I would love to hear them.
I have never failed to separate doers from other types.
The only issue I had is that sometimes, after interviwing 20-30 people, I could not find a 100% doer, and therefore I had to make a comromise.
I think they're completely missing the point of those comments, but regardless of that, I think there's a bigger point to be made here.
Over the years, I've noticed there are two types of developers: the ones who only want to work on interesting code/new projects/etc, and the ones who get shit done.
The first guy does NOT want to do any maintenance, only wants to work on new projects so he can get things "his own way", throws a hissy fit or refuses to do it outright when he has to dig through tons of horrible legacy code, etc.
And the second guy just gets shit done. No matter what it is, he understands that it just NEEDS to be done, and does it. He will not take it silently - sometimes, just like the first guy, he will be loud and obnoxious in voicing his opinion that this code totally sucks, what moron wrote this, and we should totally rewrite it, etc.. but then he sits down, rolls up his sleeves and does it (and then works on re-writing it in the right way, if there's time).
The first guy might be a much better programmer than the second. He will pass a technical interview with flying colors, he's usually up to date on all the latest technology, he's good and he knows it.
But after a few years of doing this, I will hire the second guy EVERY TIME.