Great question and thank you for making the rest of us think about it because it can become unnecessary or burdensome when used inappropriately. I personally e

Great question and thank you for making the rest of us think about it because it can become unnecessary or burdensome when used inappropriately. I personally eschew the trivial or otherwise stupid company standards in favor of more language/community set standards (think PEP8). When I do criticize I will lead more with “what was your reasoning behind <this block of code>” because you get a more honest response and sometimes you’ll get the author to admit to “oh I was just being lazy there” or “do you have a better way of writing that”. Code reviews are a necessary evil but how you approach them can change the outcome.