Common mistake:

1 . Help the reviewer

2. Anticipate questions

aka, "if your code was hard to write, make it easy to understand"

3 . Care personally but challenge directly

4. Suggest ALL possible improvements

5. Have high standards

6. Allocate time for reviewing code

7 . ASSUME GOOD INTENT.

“An amateur is defensive. The professional finds learning (and even, occasionally, being shown up) to be enjoyable; they like being challenged and humbled, and engage in education as an ongoing and endless process.”

— Ryan Holiday, Ego Is the Enemy