aevaone of the more useful things I realized at some point for how to be a good code reviewer is "that's not how I'd do it" is not constructive feedback and is not a valid reason to request a change, and if you can't think of an actual good reason to block a review, you can save a lot of time for everybody involved by just chilling out about it
Will@aeva I'll often leave that sort of comment as *explicitly nonblocking* commentary, "I would consider doing this like this because blah blah blah, see what you think" sort of thing. I like this for three reasons: (a) I'm not holding up anyone's work; and (b) hopefully I get to teach somebody something, which is great; and (c) hopefully people will take my example and do the same thing for me so I'll get to learn something, which is also great.
Code review as a toxic reflection of bad culture is unfortunately prevalent, though, and I will fully grant that trying to introduce this style of commentary into such an environment may not go well. =(