Looking at the comments, Having emotions is normal, but at work we should try stay professional. In the article there is a reference to his own bugs and during code review what he called a nitpick. I found that a bit immature, should we wait until its a bug in production?
I think the industrie would benefit if we all abide by egoless programming.
Are you saying everything brought up during a code review is relevant, i.e. that nitpicks just don't exist at all? Because I feel that's a rather extremist point of view.
Note that a bug isn't a nitpick. A nitpick would be something like "that variable name is a bit long" - it may be, but is it really relevant in a business sense? Should either reviewer or programmer be spending time on something like this? Should it hold up an important commit?
Protesting that isn't 'immature', it indicates he understands there is a trade-off between differing priorities. It's something that is surprisingly uncommon among programmers, unfortunately.
I think the industrie would benefit if we all abide by egoless programming.
https://blog.codinghorror.com/the-ten-commandments-of-egoles...