Recently I asked my manager if we could try this at my work. He was very supportive. Previously my project has done peer reviews with great success. However the practice has fallen to the side due to the normal pressuress of software development.

Thanks for the post.

You may not be able to automate everything away, as many people of the geek mentality appear to believe. I happen to be a huge proponent of using technology for what it is good for and find people trying to use it in incorrect ways abhorrent.

Let me know your thoughts

=) Huge fan and follower.

You may appreciate the many responses to your videos from on my blog. Keep up the good, clear, rational thought process.

I review two people code on a regular basis, both are back end apps and notorious for crappy adherence to standards or anything else for that matter, so i get my times worth.

My question to you is… when i submit my code changes for review how do you think i should respond when i get a failure in response? How should i react when they come back the fourth time and have just refused to notice the semi-colon on the end of my if statement?

The best way to keep costs down (and support the business) is to catch bugs as early as possible and BEFORE they are found by the public.

This way you can also get the code review tool to check the validity of the review. Reviewers can mark a line they don’t like, like a game of minesweeper. If they submit and they haven’t marked a tainted line then it rejects their review.

Damn that’s evil… ;-)

I agree that design decisions should be made and approved before the actual coding starts.