10 Commandments of Navigating Code Reviews
summary
Ten concrete rules: a list of ten guidelines that aim to help underrepresented contributors navigate biased and rude feedback, backed by a cited study that GitHub reviewers get harsher when they know a submission is from a woman. Specific tactics include thou shalt not take it personally, detach from the code, accept good suggestions and articulate why when keeping your solution, offer offline collaboration after stalled threads, contribute to others co-reviews, learn from comments so you don’t repeat mistakes, and fix nitpicks promptly so reviews stay productive.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:45Dont take it personally
- 3:57Take that ring off
- 6:26Acknowledge your solution
- 8:04Collaborate offline
- 9:03Contribution to others
- 10:00Treat submitters how you want
- 10:55Dont be intimidated by comments
- 12:59Dont repeat the same mistakes
- 14:28Embrace the linter
related talks
44mSurviving Code Reviews
30mCode Reviews Using Art Critique Principles
52mTeaching through Code Review
45mTen Commandments of a Software Engineer
34mThe 10 Biggest Mistakes You Shouldn’t Make In Open Source
48mJudging a book by its cover - how inclusive is your community?
25mCode Review of Senior Python Engineers
01h 01mReviewing Beginners' C++ Code