[Taro Classic] How To Make Code Review Amazing
![[Taro Classic] How To Make Code Review Amazing poster](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fevent_images%252F1752792564-image.jpg%3Falt%3Dmedia%26token%3D8b352627-4bc1-4fc0-af34-11e6d7519bdf&w=3840&q=75)
At any real tech company, you can't just merge your code straight to production - It has to go through code review first. For junior engineers in particular, this can be particularly daunting as their pull requests get riddled with comments and are stuck in review hell for days. If you're more senior, you now have the conundrum of how to leave insightful feedback.
That's what this course is here to help with. We want to give you the skills and confidence to make code review amazing on both ends, for the author and the reviewer. After going through this course, you will:
- 💡 Understand the core benefits of code review
- 🎯 Know what optimal code review discussion looks like (hint: it’s not linter comments)
- 🛠️ Have an arsenal of tactics to level up your pull requests so they sail smoothly through code review
- 🤝 Write code review comments that are both constructive and empathy, deepening relationships on your team
- 🌱 Build a healthy code review culture within your team
As tech leads and managers, Alex Chiou and Rahul Pandey know the importance of code reviews, having gone through 10,000+ of them.
Alex Chiou: At Meta, Alex was one of the most prolific code reviewers in all of Instagram, reviewing 700+ diffs per half in his final years there, putting him in the Top 1% of code reviews. He wasn't writing short comments either - Alex had the most lines of code review comments by volume by a wide margin across his entire organization of 100+ engineers, often writing paragraph long comments to mentor his teammates and teach them better engineering practices. As a tech lead, he built a culture where engineers would fight to review each other's diffs as quickly as possible, creating a review turnaround time of less than 4 hours!
Rahul Pandey: At Meta, Rahul had the unique TLM (tech lead manager) role where he mentored many engineers on how to make the code review process effective, both when writing diffs themselves and reviewing those of others. His code review fundamentals are also excellent from his exposure to many different languages - At Meta alone, he worked in 8 different programming languages!
