The document summarizes best practices for conducting educational code reviews. It discusses that code reviews ensure quality, sync the team, and allow people to learn. It then provides tips for how to conduct effective code reviews, such as complimenting, empathizing with, guiding, explaining to, and connecting with the person being reviewed. The document emphasizes that reviewing code takes patience, practice, and passion. It concludes by thanking the audience.
12. Compliment
• “Great job on …”
• “I really like that you …, outstanding!”
• “I wasn’t expecting that you would do … as a …”
13. Empathise
• “Don’t feel bad for not understanding this”
• “Believe me, you can do it as well!”
• “I know it’s hard, everybody takes time to overcome it”
14. Guide
• “Here’s a hint, you can check out …”
• “I encourage you to try searching …, …”
• “I challenge you to try out … and see …”
15. Explain
• Explain why for everything
• Variable naming, refactoring, using another method, etc.
• “The reason is that …”
• “It may not seem obvious at first, but …”
16. Connect
• Articles, Talks, Communities, Papers, Videos, etc.
• Explain why you connect them
• “I suggest you check out this great article, it … very well”
17. As a Reviewer
• It takes patience
• It takes practice
• It takes …… passion!