This is a few days late, but wanted to write it anyway to keep the discipline and routine going.
I subscribe to several really high-quality newsletters and one post last week was of immense use. It was Exactly What to Say in Code Reviews by Jordan Cutler.
Getting the tone, content, and style right in code reviews is a significant part of collaborating in engineering teams. It involves many trial-and-error iterations, a lot of self-reflection, and an understanding of the culture of the team you’re on.
So, Jordan’s post was like getting a well-constructed, time-tested, and solid toolbox for Christmas, for this part of engineering work.
I applied some of the principles while doing code reviews last week. I actually brought up the post and put it side-by-side with the pull requests.
Judging by my coworkers’ replies and comments, I knew that I had carried out some effective strategies.
Thank you, Jordan!
