Comments on: Code reviews before every commit? http://www.techyouruniverse.com/software/code-reviews-before-every-commit Musings about technology from a Geek Thu, 20 Nov 2008 10:29:49 +0000 http://wordpress.org/?v=2.3.1 By: Pete http://www.techyouruniverse.com/software/code-reviews-before-every-commit#comment-701 Pete Tue, 25 Mar 2008 22:53:27 +0000 http://www.techyouruniverse.com/software/code-reviews-before-every-commit#comment-701 Well put Nick. Though I would argue that *every* commit is not necessarily the right approach in most places. We trust the author to initiate code reviews, this enables trivial changes to go unreviewed but more importantly it doesn't hamper "commit early commit often". The developer then starts a code review for a logical piece of work, which is usually multiple commits and usually associated with an issue/story. We think code review is such an underrated process we wrote a tool to make it easier Crucible (atlassian.com/crucible). There is another commercial tool CodeReviewer from SmartBear that is more formal than Crucible and a couple of open source alternatives as well (CodeStriker and Jupiter). Well put Nick. Though I would argue that *every* commit is not necessarily the right approach in most places. We trust the author to initiate code reviews, this enables trivial changes to go unreviewed but more importantly it doesn’t hamper "commit early commit often". The developer then starts a code review for a logical piece of work, which is usually multiple commits and usually associated with an issue/story.

We think code review is such an underrated process we wrote a tool to make it easier Crucible (atlassian.com/crucible). There is another commercial tool CodeReviewer from SmartBear that is more formal than Crucible and a couple of open source alternatives as well (CodeStriker and Jupiter).

]]>