code review

  • Making code review software tools help, not hinder

    Posted December 29, 2008 - 11:02 am

    Tools can certainly assist in the code review process -- particularly in ensuring that the code adheres to corporate style, collecting metrics and applying departmental programming policies -- but some caution that you shouldn't depend overmuch on them.
  • How NOT to run a code review

    Posted December 29, 2008 - 10:59 am

    Code reviews can become meetings from hell: politically, technically and in terms of process.
  • Doing spot-on code reviews with remote teams

    Posted December 29, 2008 - 10:56 am

    It's hard enough to run an effective code review when everyone is in the same room. But when developers work at home, contribute to open-source projects, or telecommute from outsourced suppliers, the challenges are intensified. Making a code review work in those circumstances requires a bit of extra effort.
  • Five reasons to do code reviews

    Posted December 29, 2008 - 10:49 am

    If you think that all you'll get from running effective code reviews is slightly better software, you need to think again. Here are five not-so-obvious reasons for code reviews.
  • Running an effective code review

    Posted December 29, 2008 - 10:44 am

    It's one thing to say you're going to do code reviews. And it's another thing to know how to go about the process right, so that the end result is the best, most joyful application possible.
  • How to lead a code review

    Posted December 29, 2008 - 10:39 am

    If you're going to do code reviews, it makes sense to do them well.
Join us:






Join today!

See more content
Ask a Question