How to Do Code Reviews Like a Human
&gt; Let computers do the boring parts<p>It&#x27;s hard to overstate the positive changes having good test coverage can make on your code reviews. You get to switch from discussing potential mistakes to discussing strategy, almost wholesale.<p>&gt; Never say &quot;you&quot;<p>Do use &quot;you&quot; when complimenting someone. Think twice when critiquing them.<p>There was a fabulous article that passed HN once on how to communicate with optimism. <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12298898" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12298898</a><p>The main point I took away from it was to use specific, personal and permanent language when complimenting someone. Use general, impersonal, and temporary language when criticizing someone. Positives are things people get personal credit for, negatives are forgivable temporary behaviors that can change and everyone is prone to.<p>&gt; Tie notes to principles, not opinions<p>Like most programmers, I automatically enjoy discussing principles. But, most often principles <i>are</i> opinions. I try to keep them out code reviews when I can (which is perhaps the majority of the time, but definitely not always). I like to focus solely on what works and what needs to be done, if I can. Being too &quot;principled&quot;, in my experience, often leads to not looking for, and not understanding situation specific reasons to go against a given principle, or to prioritize one principle over another. Plus, almost everyone is applying their principles when they code, it&#x27;s just frequently not the same principles you think of when you review the code.