👍 Looks GREAT To Me: Getting Past Bare Minimum Code Reviews
summary
Actionable checklist: require local linting/formatting and CI tests during development, split large changes into under 500 lines and ideally <20 files, auto-assign via CODEOWNERS and use PR templates listing reproduction, root cause and tests, review in 25–45 minute bursts, label comments as needs change / needs rework / nitpick, prefer objective Triple R: request + rationale + result, take long threads offline and always document the outcome, and add informational reviewers to break single-person bottlenecks.
AI-written summary · about
chapters (7)
- 0:00Better code reviews
- 2:33What reviewers do wrong in code reviews
- 9:00Improving feedback
- 22:52Preparing for reviews
- 29:13Fixing common author mistakes in PRs
- 35:48Beyond bare minimum
- 46:30Team review culture
related talks
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
23mAsync non-blocking code reviews
45mKeynote: On the Care and Feeding of Feedback Cycles
01h 29mBetter Code and Collaboration through Open Source Concepts, Dev Containers....
31mDevOps 2.0 - Bigger, Badder with More Automation
51mVersion Control tips, tricks and good citizenship
58mDeveloper Joy – How great teams get s%*t done
39mDev Team Metrics that Matter