40e: Tell the other side what's been left out

While receiving a code review, we need to express ourselves and coach the other person. There is a reason for any decision we make. Sometimes, people don’t see these reasons. Instead of insisting on being right, we need to tell the people what’s been left out in the feedback/review we receive. If the decisions are not explicit (such as with ADRs), it’s not easy to see implicit decisions even if the code is well written.

• Related Note(s):
  • 21: Efficient Code Review Process (The changes I wanted to do in one of my teams);
  • Maximizing Personal Growth by Understanding Feedback You Get;
• Source(s): Thanks for The Feedback by Douglas Stone & Sheila Heen

This note is mentioned in: