In this episode I cover some aspects of the code review process.  Some good and bad practices as well as some recommendations as to how to tackle a code review from the reviewer and the reviewee.

Main concepts takled:

1. Code review should be part of every dev process.
2. Establish a secure place during a CR session.
3. Coming into a code review expecting problems.
4. As the dev being reviewed, you should have a chance to explain your work, this is not just about getting told you're bad.
5. A CR session should never be personal.
6. As a reviewer you have to remember that this might be a stressful experience for the other person.
7. As a reviewer you're not automatically right, you have to be open to be corrected and learn through the review process.
8. The CR sessions is not the moment where you find big bugs, if that happens, then there are other problems (like lacking unit tests, etc).

 

Get in touch!

• X (Twitter): https://twitter.com/deleteman123
• YouTube: https://www.youtube.com/@the-scripting-den

Rate us!
To ensure the podcast reaches more developers, make sure to rate it on your favorite podcasting app and in Podchaser!
Thank you!