Code Review

I think I need to introduce code reviews at work.
Some links I've found so far, saving here for future reference:

  • http://www.codinghorror.com/blog/archives/000495.html
    After participating in code reviews for a while here at Vertigo, I believe that peer code reviews are the single biggest thing you can do to improve your code. If you're not doing code reviews right now with another developer, you're missing a lot of bugs in your code and cheating yourself out of some key professional development opportunities. As far as I'm concerned, my code isn't done until I've gone over it with a fellow developer.
  • http://www.developer.com/java/other/article.php/3579756
    Code reviews, however, don't have to be painful.
  • http://it.toolbox.com/blogs/puramu/tips-for-a-successful-code-review-12946
    There are not many things a manager of developers can do that has the potential to go as spectacularly wrong as a code review.
    There are not many things a manager of developers can do that has the potential to go as spectacularly wrong as a code review.
  • http://www.macadamian.com/index.php?option=com_content&task=view&id=27&Itemid=31
    Code Review Checklist
  • A book, Peer Reviews in Software: A Practical Guide, Karl E. Wiegers, first 2 chapters here.

    any body else have an opinion?

Leave a Reply

Your email address will not be published.