Inclusive Tech: Conducting Humane Code Reviews
42mIntermediate2020-12-21
Authors

Adrienne Braganza Tacke
Author, Engineer, Teacher
Course details
Learn how to conduct fair, objective, and productive code reviews and still like your teammates afterward! Instructor Adrienne Braganza Tacke explains why we conduct code reviews, the main pain points teams experience, and what your team needs to make code reviews successful. She explores objectivity and how to write constructive feedback, covers why your team needs a working agreement and how to create one, and offers tools and automations to make the process faster and easier for your team. Successful code reviews have an inclusive mindset, so Adrienne also steps through how to master writing any kind of code review comment, even constructive feedback, and covers how to formalize an enforceable code review process. With buy-in from the whole team and a clear, detailed process laid out, process loopholes should be minimized and hopefully eradicated for good.
Skills covered
Software Quality AssuranceTech Career SkillsCybersecurityCloud ComputingData ScienceSoftware DevelopmentDeep Dive (X:Y)
Concepts
0. Introduction
- 01 - Code reviews - heated, but needed
1. Why Do We Perform Code Reviews
- 02 - Goal 1 - Catch design flaws
- 03 - Goal 2 - Ensure code clarity and coherence
- 04 - Goal 3 - Validate necessity
- 05 - Goal 4 - Confirm functionality
2. The Working Team Agreement
- 06 - What's a team working agreement
- 07 - Why does my team need a team working agreement
- 08 - Challenge - Create a team agreement
- 09 - Solution - Sample team agreement
3. Developer Pain Points in Code Reviews (AKA, What Not to Do )
- 10 - Subjectivity
- 11 - Tone of voice
- 12 - Process loopholes
4. Strategies for Better Code Reviews
- 13 - Objectivity
- 14 - Tools of objectivity
- 15 - TL DR Don't be a jerk
- 16 - Team working agreement to the rescue
- 17 - Challenge - Your code review challenge
- 18 - Solution - Your code review challenge
Conclusion
- 19 - Your code reviews