I saw this website today in this thread [0]. It made me more curious about bike-shedding which I've known about for a while. I realized that during code review

I saw this website today in this thread [0]. It made me more curious about bike-shedding which I've known about for a while. I realized that during code review I often do exactly what the article mentions: focusing on the small, tangible details rather than the things that actually matter. How do others deal with this issue? Should minor but impactful issues be ignored during code review? How can I effectively review a large commit that I don't quite grasp, or that changes code that I'm unfamiliar with? How can I steer my team (and myself!) away from bike-shedding given that it's more-or-less part of human nature? I'm curious about what others think. [0] https://news.ycombinator.com/item?id=29770105 https://news.ycombinator.com/item?id=29770105