Not OP here. Code reviews, to me, are opportunities to 1) Catch edge use case / business requirements misunderstandings 2) Mentor new hires/junior engineers o

Not OP here. Code reviews, to me, are opportunities to 1) Catch edge use case / business requirements misunderstandings 2) Mentor new hires/junior engineers on the ways things should be done (e.g. internal culture about some architecture/design). BUT, I absolutely despise code reviews that nitpick on non documented or 'because I prefer that way' stuff: 1) Task tickets that only have a vague description, have their own 'play detective' about the requirements, but a lot of new ones surface during code review. 2) Requirements are met, but there are internal/personal technical directives that are written nowhere, are not enforced with automated checks and may dramatically change a feature/patch is implemented (I can only think about that guy that worked in a company in which only LEFT JOIN sql statements were allowed). Fuck that noise.