3 ms·
I have also found a "reverse" effect. Engineers in general (not just software guys), tend to not assign blame to errors, especially in panic situations. People
by sergiosgc 10y ago
I have also found a "reverse" effect. Engineers in general (not just software guys), tend to not assign blame to errors, especially in panic situations. People declare errors as a matter of fact ("the database load is beyond the roof"), not as a result of wrongful actions ("your commit thrashed the database").
Both ends of behavior are the result of being confronted often with error, be it caused by wrongful action or caused by externalities. When a circuit goes up in smoke, its just physics being a harsh mistress; getting angry about it is useless, so we just skip the blame/anger part.
- mcguire 10y agoI'm afraid I have to disagree, partially. In any given situation, you're right. But it's often necessary to get programmers to change their behavior, since what they are doing is causing the problems, and programmers are no better than anyone else at changing behavior in response to criticism. Design and code reviews are particular hot spots, which is why most I have seen had become just check offs.