There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter

Goals of Code Review

Code reviews are a necessary part of any development process. To make code reviews be a pleasant experience, both the developer and the reviewer need to keep an open mind. That doesn't mean that the developer can't defend something that they think is good work, or that the developer cannot comment when they feel something should be improved.

As a developer, look at code reviews as an opportunity to showcase the code to peers. As a reviewer, ask questions and allow the developer to explain choices he or she made in the process. Both parties should not push something without a good explanation. If an agreement on an issue cannot be made, involve a third party that is trusted by both sides. Do not take it personal, opinions can differ and there is always more than one way to reach a goal.

Copyright © 2015 by Julian Easterling. SOME RIGHTS RESERVED.

Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.


All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.