Lately, I’ve been reading articles about best practices for code reviews. I notice that these articles focus on finding bugs to the exclusion of almost every other component of a review. Communicating issues you discover in a constructive and professional way? Irrelevant! Just identify all the bugs, and the rest will take care of itself. So I had a revelation: if this works for code, why not roman
![How to Do Code Reviews Like a Human (Part One)](https://cdn-ak-scissors.b.st-hatena.com/image/square/354ef0eea5d39d79592c550215d2db5fd29532c7/height=288;version=1;width=512/https%3A%2F%2Fmtlynch.io%2Fhuman-code-reviews-1%2Fcode-reviews-cover1.png)