|
A low self esteem from constant insults (aka non-constructive or overly harshly presented critique) or lack of encouragement will kill anybody's ability to accept useful feedback, and people can certainly become numb to that. However, that numbness is different than being unaccustomed to taking useful critique without getting defensive. Which is absolutely a learned skill– one of the most important you learn early in art school. Someone unaccustomed to any critique, or only used to complimentary feedback will bristle at any criticism. Someone used to constructive critique will still bristle at insults, intentional or not, so the EQ of the critic in delivering the message is also critical. The biggest enemy here are people who think that their criticism can be as rude, pedantic, or imperious as they want if the core point is valid. That might provide comparable results for the issue at hand, a) but human beings don't deserve to be treated like that, and b) it kills morale, which kills productivity, quality, retention, etc. It blows my mind how many fully-grown adults can't see that they're only quieting their own insecurities with unnecessary harshness, and that they're essentially stealing self-esteem from the team by indulging that urge. Having people on your team with poor enough mental hygiene that they need to position themselves above someone else to feel good is a serious problem. I think it's one of the things people really mean when they talk about overly macho bro types or neckbeards. |
ok firstly Comments about the individual in a CR is way out of line.
There is a massive difference between "This code will fail in <a certain way>" and "You failed <, again, like you always do>" ... The latter is out of line and should be addressed head on with a manager present or a person who will enforce it's toxicity.
Now that said, criticism of code should always been allowed. It either has certain properties or it does not. A discussion of economics (scope/timelines/applicability) are a middle ground. But either the code has a race condition or it doesnt. It's easily read (which is best judged by the reader, not the writer)... It's missing some property that is desirable.
If one takes a criticism of code as a criticism of self, that is ego crossing over to where it doesn't belong. I like to remember The bridge will either hold the load or not regardless of how one feels about it. "This wont hold 1 ton" is better information than "Have you considered what happens if you put 1 ton on this?" .. The former informs you of something that must change, the latter leaves uncertainty and obscurity where infact the answer is already known.