One thing I find helpful is to write out every possible thing I could have an issue with in a code review and then pick the most important comments and drop the rest. You start realizing what is actually bad and what is just a different style.
Years ago, I used to write more on my blog about how to conduct code reviews without demoralizing people. If memory serves, I once wrote a satirical post called something like "How to Use a Code Review to Execute Someone's Soul." IIRC, that popped on Reddit/Hacker News.
Anyway, for a decade, my message regarding code reviews has always been what you're saying here. "You're going to find dozens, or even hundreds, of things that you'd do differently. Jot them all down, prioritize them, and then share 5, max. Anymore than that, and you just demoralize people. Leave the rest in the codebase -- we can fix code later, but we can't fix demoralized teammates later."
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One thing I find helpful is to write out every possible thing I could have an issue with in a code review and then pick the most important comments and drop the rest. You start realizing what is actually bad and what is just a different style.
That is such a GREAT strategy.
Years ago, I used to write more on my blog about how to conduct code reviews without demoralizing people. If memory serves, I once wrote a satirical post called something like "How to Use a Code Review to Execute Someone's Soul." IIRC, that popped on Reddit/Hacker News.
Anyway, for a decade, my message regarding code reviews has always been what you're saying here. "You're going to find dozens, or even hundreds, of things that you'd do differently. Jot them all down, prioritize them, and then share 5, max. Anymore than that, and you just demoralize people. Leave the rest in the codebase -- we can fix code later, but we can't fix demoralized teammates later."