https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/ https://blog.codinghorror.com/the-ten-commandments-of-egoles... I think of this in t

https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/ https://blog.codinghorror.com/the-ten-commandments-of-egoles... I think of this in two ways. First, in a team, we're all collaborating on the project. Different people have different ideas and different experience, and debating can make for better results. In my last job, there was one particular person I disagreed with all the time (down to hops vs malt) but for that reason was a great person to collaborate with. Second, there's code review. My last place was very much into its style guides and best practices at the individual PR level (but remarkably bad at higher levels; the prevailing large-scale design rule being ‘ship the org chart’). I think of that sort of code review comment much like a compiler or analyzer message: sometimes it's right, and caught a mistake. Sometimes it's a false positive, and you just have to change something to make the tool shut up. (Third, I wouldn't be able to recognize an actual personal attack unless it were extremely blatant.)