It Takes More Than LGTM to Do A Proper Code Review

on YouTube ↗47m

" summary

An engineer recounts a real review that changes 6,000 lines and takes two weeks to review and then lays out concrete tactics: run CI, coverage and style checks automatically, keep style-only changes in separate PRs, use draft pull requests or feature branches to get early feedback, read tests first, and track metrics (lines changed, time-to-review, comments — GitLab shows merge requests taking 41 days). Practical, tool-specific fixes and measurable targets for reducing cycle time.

AI-written summary · about

" chapters (16)

1. 0:00Introduction to code reviews
2. 3:57Speaker background
3. 5:01What is a code review
4. 8:16Why we do code reviews
5. 11:48Social aspects of reviews
6. 17:03Automating code review tasks
7. 18:30How I review code
8. 21:20Preparing your pull request
9. 23:06Promoting pull requests
10. 25:13The problem with large PRs
11. 28:50Solutions for large PRs
12. 31:39Ideal PR size and workarounds
13. 34:28Improving team alignment
14. 36:14Using data to improve reviews
15. 40:34Key takeaways
16. 40:59Q&A session

" related talks

• 32mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Infobip Shift 2023
• 41mCracking the Code Review from Guesswork to Automated GuidancePaco van Beckhoven · Code Quality Conference 2024
• 17mThe Perfect Code ReviewVictor Rentea · Conf42 Enterprise Software 2021
• 01h 05mGetting Good (or Better) at Code ReviewsRhia Dixon · NDC Melbourne 2025
• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days Ticino 2025
• 46mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Voxxed Days Thessaloniki 2023
• 44mEffective Code ReviewDave Liddament · phpDay 2018
• 47mGoldilocks and the Three Code ReviewsVaidehi Joshi · Red Dot Ruby Conference 2017