))
Episode 14 - The art of code review
Manage episode 411013646 series 3546970
Content provided by Fernando Doglio. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Fernando Doglio or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
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:
- Code review should be part of every dev process.
- Establish a secure place during a CR session.
- Coming into a code review expecting problems.
- As the dev being reviewed, you should have a chance to explain your work, this is not just about getting told you're bad.
- A CR session should never be personal.
- As a reviewer you have to remember that this might be a stressful experience for the other person.
- As a reviewer you're not automatically right, you have to be open to be corrected and learn through the review process.
- 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!
36 episodes
Share
