Drama-Free Code Review!
summary
Advocates a concrete, enforceable PR checklist (unit tests, no test regressions, dependencies, style) and shifting mundane checks to automation with tools like black, flake8, pylint, SonarQube and platform reviews (GitHub/GitLab/Bitbucket). Recommends small PRs, timely responses, reviewers asking questions instead of ordering renames, and highlighting positives. Cites a 2015 Microsoft study: harsh comments are useful 57% of the time versus neutral comments 80%. Goal is faster, less confrontational merges by focusing human review on what tools cannot catch.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:15Code Review Process
- 2:52Variables
- 3:55Creating and Submitting a per Request
- 4:31Adding the Right People To Review
- 5:34Pr Checklist
- 6:40Reviewing the Product List
- 9:20Why We Are Doing Code Review
- 16:07How Can I Do an Efficient Code Review Process
- 18:42Second Point Be Kind
- 21:26Golden Rule
- 21:39References
