Comment by rawgabbit

This is my take on the article using your example.

1) Do not use judgmental language (e.g., sort out your code); instead use language that is asking for clarity or asking for more information (e.g., the code has issues A, B, C; any reason why the code cannot be refactored?).

2) Do not assume the other person is stupid (e.g., wastes my time); instead use language that addresses the problem (e.g., please see best practices document 1.2.3 and 4.5.6 to how it should be written.)

3) Do not use cold language that makes you distant and detached (e.g., This is the third time your code has these issues); instead use language that you would use to a friend (e.g., Is there something going on that I should know about?)