Great article, and I mostly agree. I want to nitpick on > Don’t review with a “how would I write it?” filter _Thinking_ about "how would I write it?" when re

Great article, and I mostly agree. I want to nitpick on > Don’t review with a “how would I write it?” filter _Thinking_ about "how would I write it?" when reviewing code catches a lot of stuff for me - I want to be able to come up with how I'd do it, see how the PR does it, and then check if the approach matches. If not, there's something to be learned and explained here. Although, all of that is in my head! If I come to the conclusion that the presented approach is wrong or inferior in an objective way (say, doesn't handle corner cases neatly or at all), I'll comment. Otherwise, let people do their thing! So, I agree with the point of not using this to generate a lot of comments, but I do believe in it as a useful technique to engage the brain, instead of just loosely scrolling over the diff.