Earlier quoted context omitted.
> I have found programmers to be far more receptive to blunt criticism than my other non-programmer friends. The work of a programmer is to sit in front of a soulless machine that has no inhibition in telling the programmer made a mistake on his code at regular intervals. You need to be pain intolerant to be a programmer, while in other roles pain avoidance is the norm.
Actually, a machine never accuses you of being the responsible of that error. It usually says "there's an error in the line..." but never addresses it towards the programmer even though they know that they are the responsible ones of that mistake. And in fact, that is one of the techniques of conflict management between partners, addressing the problem instead of finding the responsible of it.
"@Dave, you seem to have made yet another type error on line 56. @jon recently committed code that didn't fail any integration tests. Why can't you be more like @jon?"