Level up your code reviews
summary
Four concrete lenses guide code review: readability lens (look for intention-revealing names, PR descriptions, tests-as-docs), perf/scale lens (ask about concurrent requests, query cardinality, indexes; read Designing Data‑Intensive Applications), and a UX lens plus conventions. Use linters, on‑commit hooks and CI to offload nitpicks. Two engineers on one team build an emoji‑prefixed system to mark blocking vs optional feedback. The talk promises practical checks, tooling and a surprising 200 slides in 10 minutes stunt.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:25Junior engineers anxiety
- 2:48Code review benefits
- 3:51Code review limits
- 4:12Readability and context
- 5:14Performance and scale
- 6:35User experience
- 8:00Team conventions
- 9:02Empathy in feedback
related talks
17mThe Perfect Code Review
46mLevel Up Code Review: How to Get the Most Out of It
40mCode Review - How to Do It Better?
29mCode review, do you speak it?
49mBetter Code Reviews FTW!
20mConducting Humane Code Reviews
11mUplifting the Art of Code Review from Testing Perspective
01h 01mBetter Code Reviews FTW!