“the best way to have it is by talking, which is an unbelievably high-bandwidth communication channel compared to those little text boxes.

In other words, code should be pair-reviewed as well as pair-programmed. For example, Aisha and Chiku could get on a screen-share and look at the code together, asking questions, making suggestions, explaining ambiguities, and highlighting potential problems.

Tone of voice and even facial expressions convey a lot of extra information that would otherwise be lost, and somehow, people are always gentler and more respectful to each other in person than they are when typing messages back and forth.

…

Pair review like this isn’t always possible, though, so when a code review happens textually, that means we need to *take even more care about what we say and how we say it* ” (emphasis, mine)

— John Arundel, on code review in “Death of a thousand nits”

https://bitfieldconsulting.com/posts/code-review

Tone of voice and being kinder than you need to be is something I’ve hammered into my young mentees, since … well, ever since I’ve had young mentees

Also grateful to @pradhvan, @mandarvaze and #AnjaliPardeshi for being kind to me when I worked with them!

#AnjaliPardeshi