This month I want to highlight a Stack Overflow blog, How to Make Good Code Reviews Better, by Gergely Orosz. This blog differentiates between good code reviews and great code reviews by advocating for thinking big picture as you review the code. We perform code reviews daily as part of our job, this blog does a wonderful job articulating how to think strategically even when looking at tactical implementations. Don’t evaluate what is written, instead think of why it was written and craft your feedback appropriately. This mindset goes beyond code and applies equally to the business side when reviewing business docs.

https://stackoverflow.blog/2019/09/30/how-to-make-good-code-reviews-better

“Better code reviews look at the change in the context of the larger system, as well as check that changes are easy to maintain. They might ask questions about the necessity of the change or how it impacts other parts of the system. They look at abstractions introduced and how these fit into the existing software architecture.”