Teaching through Code Review
summary
Argues that code review becomes a teaching tool not a gatekeeper: use prettier and linters to automate formatting, run tests on GitHub pull requests, require two approvals in Jira/Bitbucket, and budget review time (example: four of ten hours). Shows PHP examples where clearer names and a single‑line operator reduce bugs, points out UA sort by reference pitfall, recommends short reviews, early pair sessions or live JetBrains-style collaboration to build team knowledge.
AI-written summary · about
chapters (11)
- 0:00Why code review matters
- 3:41Consistency in teams
- 8:58Teaching through code review
- 12:35Knowledge sharing benefits
- 19:00Writing readable code
- 20:45Negative feedback pitfalls
- 23:56Constructive review comments
- 28:09Accidental code reviews
- 33:06Asking for help
- 39:52Pair programming vs reviews
- 45:56Q&A
related talks
30mCode Reviews Using Art Critique Principles
34mWhat I Learned about Code Review Teaching 8th Grade Poetry
25mCode Review of Senior Python Engineers
01h 22mKeynote: Growing Better Programmers
41mThe way we teach tech
36mTeach Your Way To Better Code
30mLessons Learned: A Developer's Perspective on Teaching & Learning
01h 01mReviewing Beginners' C++ Code