-
Code Reviews Considered Harmful - by MTaylor. "In short, if a coding standard can’t be enforced mechanically (ie with a linter in the build), citing an industry standard, or referring to a group wide standards document it ought to be disallowed from a code review. That way we can all focus on finding bugs, logic errors, and security vulnerabilities."
-
Code Reviews in an Agile, Fast-Paced Environment - by Farnoosh Azadi. "Here at OnlineSales.ai, we’ve seen code reviews having a deep and lasting impact on quality of code shipped. It acts as an excellent tool for mentoring of new hires, for setting a clear coding standard that helps keep our code base clean and consistent and as a bonus, it even helps promote re-usability of existing modules that developers may not have been aware of!"
-
Giving and Receiving Great Code Reviews - by Sam Jarman. "In summary, as a submitter, plan, tell the story, and use the review as a learning experience. As a reviewer, slow down, check carefully, automate as much as you can and take the opportunity to improve your team."
-
Mindful Communication In Code Reviews (Slides) - by Amy Ciavolino. "Even if a reviewer followed all the tips so far, they'll make mistakes or get careless. Try to keep in mind we're on the same team and they likely had good intentions behind whatever feedback was given."
-
Three CTOs Answer: What Is Good Code? - by Roger Jin. "Code should be written for humans, not just for computers."
-
What We Learned from Google: Code Reviews Aren’t Just for Catching Bugs - by Bruce Johnson. "Contained herein are both the big, obvious engineering reasons you should adopt code reviews, as well as the more nuanced — but equally important — benefits to your customers and your own company culture."