I don't agree that code review is simply about catching style errors: that's what linters and tools like Prettier automate for you. Amongst other things code review should definitely be looking at how coding decisions conform to architecture/design goals.
We at least both agree that using real-world scenarios is a better approach than personality tests and abstract code problems :)
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.
I don't agree that code review is simply about catching style errors: that's what linters and tools like Prettier automate for you. Amongst other things code review should definitely be looking at how coding decisions conform to architecture/design goals.
We at least both agree that using real-world scenarios is a better approach than personality tests and abstract code problems :)