Painful code reviews don’t have to be that...

Painful code reviews don’t have to be that bad! While easier said than done, code reviews can and should be a collaborative space to improve code together, not a place to display power or aggression. Reviewers: be compassionate, help relieve the stress of this evaluation of one’s work through questions over declarative statements, and focus on what matters. " "" "When submitting code to be reviewed, though, do your part: double-check your code for simple misses and whatever else is essential in your specific domain. You’ll improve your code review skills and set yourself up for success with your reviewer." "" "If a lot of style issues are getting opened in your reviews, get a linter in there! Through automatic linting, your coding environment can help enforce the style rules generating so many review comments — these are never a great use of code review time anyway! Code reviews are painful, but they don’t have to be #bendevtip

---

Original post on LinkedIn