5 ms·
Well if there actually was a bug, as you state, you are clearly in the right to point it out. Both parties in a communication have a responsibility. The party c
by olavk 8y ago
Well if there actually was a bug, as you state, you are clearly in the right to point it out. Both parties in a communication have a responsibility. The party criticizing the code has a responsibility be factual, concrete and constructive, and to only criticize the code, not the personality of the author. The recipient of criticism on the other hand have the responsibility to listen and not become defensive or take criticism of the code personally.
Personally though, it also really irks me when someone carefully explains me something I already know, so I understand the mindset.
- FeepingCreature 8y ago> only criticize the code, not the personality of the author. Hence denying the author the possibility to improve. Eventually the author will be let go, and they will have no idea why or what they did wrong. This is called "being polite."
- olavk 8y agoIf you criticize the code by pointing out factual issues, then the the author can lean and improve by understanding these issues and improving the code. Calling the author an idiot does not help to improve anybody.