Thoughts on habits + practices for giving/receiving feedback effectively, as well as creating systems that get better at this with time
- Company Blogs
- Sandya Sankarram
- Michael Lynch
- Erik Uzureau
- "Writing Code for Code Review" (Forthcoming)
- Code Review Manifestos at Criteo
-
https://hecate.co/blog/code-review-review-is-the-managers-job
- May not work in all cultures/teams
- Interesting appeal to the Andy Grove / High Output Management school of thought
-
A code review manifesto: https://github.com/ppseprus/code-review-manifesto
-
Internal D&I Code Review Presentation
- Worked on this Anh-thu Huynh and Christopher Groskopf, see Google Drive
-
Managing mindset as a reviewee
-
A skit about PR review
-
10/28/2019
- https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/
- Has examples for figuring out tone (both in delivering + acknowledging)
- Defer discussions about styleguide rule to the guidelines repo rather than rehashing it on the specific instance
- Builds on this piece from thoughtbot
- https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/
-
Giving feedback in general
-
Flickr Eng Vision doc: https://code.flickr.net/2021/11/22/flickr-engineering-team-vision-guiding-principles/
- Pair Programming
- Mentorship, Coaching, and Advocacy
- Better Allies: 5 Ally Actions Newsletter
- On having common mental models for effective problem solving (since code review helps align these)
- Gitmoji CLI Tools: https://gist.github.com/ericallard0/961c4d109584595594d2baf79d7480e8