By estherschindler
via cio.com
Published: Dec 23 2008 / 21:49
You want the software development team to create the best quality code possible. Code reviews can be a frustrating waste of time, but here's how to turn it into a worthwhile experience that contributes to team-building, improves the software, and oh yeah... is also fun. This is the definitive guide (or at least tries to be -- it's exhaustive anyway!).
Comments
Mark Levison replied ago:
Oddly enough I don't agree entirely with the article: A couple of things that I feel the article fails to address:
1) Pair programming vs. Code Reviews - I think pair programming is a much better way to increase quality and reduce bugs than code reviews. http://www.notesfromatooluser.com/2007/12/pair-programmin.html
2) Code reviews at their best are conversations, tools such as Smart Bear's etc inhibit and don't enhance the conversation: http://www.notesfromatooluser.com/2006/12/online_code_rev.html use them only for distributed teams.
Voters For This Link (14)
Voters Against This Link (1)