GitHub Staff Engineer Sarah Vessels discusses her philosophy of code review, what separates good code review from bad, her strategy for finding and reviewing code, and how to get the most from reviews of her own code.

The GitHub Blog provides updates, announcements, and insights from the world's leading software development platform, covering topics such as new features, community highlights, and industry trends. Developers can learn about GitHub's latest developments, best practices for collaboration, and tips for maximizing productivity on the platform.

GitHub Blog

Sarah Vessels, a GitHub Staff Engineer, shares her code review philosophy, highlighting its significance in building quality software. She covers how she identifies and prioritizes pull requests, uses GitHub and Slack integrations, and emphasizes the importance of clear communication and consistency in code reviews. She also discusses strategies to reduce notification fatigue, uses of automation, and offers advice on providing constructive feedback. Ultimately, she aims to improve the overall code quality and foster a collaborative editing environment.

How to review code effectively: A GitHub staff engineer’s philosophy

Code review is certainly one of the hardest parts of the job. I personally use “conventional:comments” to improve readability. <a href="https://conventionalcomments.org/" target="_blank" rel="noopener nofollow">https://conventionalcomments.org/</a>

I feel like at times a code review can be omitted in favour of a linting tool 😄
<img src="https://media.daily.dev/image/upload/s--OpgELeYi--/f_auto/v1723538613/ugc/content_28253b20-12d7-4dde-b1d7-cb82c0ee2b2c" alt="image">