3 Ways To Write Deeper Comments

In this video, we explore how to give more impactful code reviews by moving beyond surface-level feedback and investing in deeper understanding and learning from experienced peers. The focus is on practical habits that help us become more thoughtful, effective reviewers.

• We rely on automation for style and formatting. It's not our job to catch syntax or stylistic issues—those should be handled by IDEs and CI systems with pre-agreed style rules.
• We review code with a clear perspective. Before reading the diff, we mentally plan how we would solve the same problem, which helps us offer more meaningful, constructive feedback beyond just approving what “looks fine.”
• We learn by watching the best. One of the fastest ways to improve as reviewers is to observe how senior engineers reject code—what they flag, how they communicate, and the patterns they look for.
• We replicate good habits. By studying thoughtful reviewers—like those who consistently flag performance issues like mobile frame drops—we can develop our own review instincts and level up faster.
• We treat reviewing as an intentional skill. There are no shortcuts; it takes practice, pattern recognition, and curiosity to become great at it. But by mimicking smart peers, we shortcut years of trial and error.