Reviewing code review duty, fun or... revenge?

on YouTube ↗13m

" summary

A concrete example shows code review decisions: a banner feature initially uses react-cookie, is migrated to localStorage, then to useSyncExternalStore before settling back because the storage event fires only across pages and component state is still required — the feature works but reviewers flag space, context and UX issues. Reviews trace motivations — Duty, Revenge, Protection, Showing‑Off, Mentorship, Friendship — and the core claim is that sustained, constructive review culture produces maintainable, safer code.

AI-written summary · about

" chapters (6)

1. 0:00Code review struggles
2. 1:54Why reviews feel bad
3. 4:01Code review chaos demo
4. 8:43Review motivations
5. 10:49Proper code review
6. 12:16Good review culture

" related talks

• 47mOpen discussion: Premises and promises of code reviewRobert Scholte, Mary Gouseti · J-Fall 2022
• 29mCode review, do you speak it?Michał Ostruszka · AgileByExample 2013
• 20mConducting Humane Code ReviewsAdrienne Braganza Tacke · WebCamp Zagreb 2019
• 10mLevel up your code reviewsDenise Yu · LeadDev New York 2022
• 37mCode Reviews: Honesty, Kindness, Inspiration: Pick ThreeJacob Stoebel · RubyConf 2017
• 46mCode Review: We Didn't Come Here to Suffer!Anne-Laure DE BOISSIEU, Pauline Rambaud · Devoxx France 2024
• 29mCreating a Code Review CultureJohnathan Turner · SREcon19 Americas
• 28mCode Review as a Collaborative Journeyhydrakecat, punchdrunker · DroidKaigi 2019