Inclusive Tech: Conducting Humane Code Reviews

Introduction

• Code reviews: heated, but needed

1. Why Do We Perform Code Reviews?

• Goal 1: Catch design flaws
• Goal 2: Ensure code clarity and coherence
• Goal 3: Validate necessity
• Goal 4: Confirm functionality

2. The Working Team Agreement

• What's a team working agreement?
• Why does my team need a team working agreement?
• Challenge: Create a team agreement
• Solution: Sample team agreement

3. Developer Pain Points in Code Reviews (AKA, What Not to Do!)

• Subjectivity
• Tone of voice
• Process loopholes

4. Strategies for Better Code Reviews

• Objectivity
• Tools of objectivity
• TL;DR Don't be a jerk!
• Team working agreement to the rescue!
• Challenge: Your code review challenge
• Solution: Your code review challenge

Conclusion

• Your code reviews