Pull My Code: Effective Code Review
summary
Argues that the Pull Request is overused and recommends shifting review left: use linters, SonarQube, TDD, contract and smoke tests, CI and trunk‑based development so commits stay production‑ready; prefer pair or short, frequent PRs and avoid long feature branches; keep commits small (stash, refactor, push) and run static analysis to remove nitpicks. Cites IBM spending $10 million on an email mainframe that overloaded in a week as a caution and urges remove code review column and linters and SonarQube for efficiency.
AI-written summary · about
chapters (9)
- 0:00Introduction to code review
- 1:24Philosophy behind code review
- 7:03Shifting left in reviews
- 9:53Learning code review culture
- 15:29Types and depth of reviews
- 15:49Practical review tips
- 21:23Pair programming benefits
- 22:26Language in reviews matters
- 26:38Summary and key takeaways
related talks
28mPull Requests: Merging good practices into your project
17mThe Perfect Code Review
16mAn unpopular opinion: Get rid of Pull Requests!
33mCode review for Open Source
45mCracking the Code Review
53mCode Review - how to do it better?
23mDrama-Free Code Review!
01h 05mGetting Good (or Better) at Code Reviews