Code Review is Undervalued

In this lesson, Adam Ernst, Software Engineer at Meta, explains why code reviews are one of the most powerful—and often overlooked—tools for influencing engineering culture. Drawing from his experience reviewing more than 1,600 code changes in just 18 months, Adam shares his philosophy on giving constructive feedback, mentoring engineers through review comments, and creating lasting improvements across a codebase. He emphasizes that effective code reviews are not about enforcing preferences but about teaching, understanding context, and helping others grow.

• Code Reviews Are a Leadership Tool: Adam views code reviews as an opportunity to mentor engineers, share best practices, and influence technical decisions in a practical, one-on-one setting rather than through broad directives.
• Explain the "Why," Not Just the "What": Great review comments focus on the reasoning behind a suggestion instead of simply requesting changes. By explaining trade-offs and remaining open to missing context, reviewers encourage learning instead of compliance.
• Create a Multiplier Effect: Constructive feedback helps engineers improve not only their current code but also the way they review others' work. This creates a ripple effect where good engineering practices spread organically throughout the team.