From the course: Inclusive Tech: Conducting Humane Code Reviews
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
TL;DR Don't be a jerk!
From the course: Inclusive Tech: Conducting Humane Code Reviews
TL;DR Don't be a jerk!
- [Adrienne] Don't be a jerk is sound advice in pretty much all of life. In the context of code reviews though, it's one of the greatest practices you can follow to make your processes much better. Now, I know what you're thinking. "Adrienne, code isn't always going to be perfect or exactly what we need. What if I need to point something out? What if there's a valid critique I need to give?" And to that, I say, "Of course, there will be code that warrants some comments from you, the code reviewer." The key is to keep in mind these three habits. First, suggest with facts. If you're going to make a suggestion in your code review, back it up. Why are you making this suggestion? What warrants this suggestion at all? If it's purely a suggestion and one that the developer can ignore, say so. If it's a suggestion based on a code review goal, also say so, and be explicit about how your suggestion may better align with that…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.