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.


This note is mentioned in:

66d.

If you're unfamiliar with Zettelkasten: These notes are atomic. The aim is to have one idea in a note. The connections between notes are as important as the notes themselves.

Reply via email

or comment below.