Code Review, you said?

on YouTube ↗46m

" summary

Argues code review is one feedback loop among many and gives concrete rules: run linters and CI and compile before asking for review, review tests first (use AAA: arrange/act/assert), request reviews early and frequently rather than blocking a release, prefer incremental reviews or pair rotation, write failing tests for each bug before fixing it (write a test for a bug), avoid truck‑factor by sharing code, remove YAGNI cruft, and frame comments as constructive, team‑focused suggestions.

AI-written summary · about

" chapters (10)

1. 0:00The importance of quality
2. 2:46Agile is feedback-driven
3. 6:17Defining feedback loops
4. 10:51Rethinking code reviews
5. 15:43Benefits of code review
6. 22:24Effective review strategies
7. 27:15Timing and frequency
8. 33:37What to look for
9. 36:58Constructive feedback
10. 42:38Building a safe culture

" related talks

• 43mCode Review, you said?Venkat Subramaniam · Voxxed Days Ticino 2024
• 40mCode Review - How to Do It Better?Sebastian Malaca · Confitura 2015
• 53mCode Review Beyond Code StyleHannes Van De Vreken · PHP UK Conference 2017
• 33mCode review for Open SourceAlex Gaynor · Open Source Bridge 2014
• 01h 01mBetter Code Reviews FTW!Tess Ferrandez-Norlander · NDC London 2024
• 53mCode Review - how to do it better?Sebastian Malaca · Voxxed Days Ticino 2017
• 29mCode review, do you speak it?Michał Ostruszka · AgileByExample 2013
• 45mHow to Get More Out of Your Code Reviews.Joe Kilner · Develop:Brighton 2021