Comments on: Developers think code reviews are great… what?

By: In-Person Code Reviews Still Prominent | >kloctalk

In-Person Code Reviews Still Prominent | >kloctalk — Tue, 06 Jul 2010 16:16:48 +0000

[...] readers know, we’ve been talking about code reviews pretty regularly here and elsewhere over the past few months. To continue that discussion, here’s a question [...]

By: Tweets that mention Developers think code reviews are great… what? | >kloctalk -- Topsy.com

Fri, 04 Jun 2010 21:22:49 +0000

[...] This post was mentioned on Twitter by Tom Pierson, Klocwork. Klocwork said: Kloctalk Blog: Developers think code reviews are great…what? http://bit.ly/aiiwdC [...]

By: Gregg Sporar

Gregg Sporar — Thu, 03 Jun 2010 01:04:32 +0000

We see a variety of responses at client sites. There is sometimes initial skepticism, but if the correct approach is taken developers tend to come around, and those who were the biggest skeptics occasionally end up as the most fervent believers. There are some key patterns that tend to lead to success:

1. Start slowly – a “beginning today we’re going to review every single line of code” approach usually doesn’t work. Pick a subset of the source base and get some quick wins to convince the skeptics. Then expand over time.

2. Set the right tone – review the code *not* the coder.

3. Spend the right amount of time – additional tips here: http://smartbear.com/docs/BestPracticesForPeerCodeReview.pdf

By: Craig Brown

Craig Brown — Wed, 02 Jun 2010 12:37:46 +0000

It's funny. When I had the opportunity to get a code review a few weeks ago I jumped at it and so did my developers. They wanted to have some external feedback about their work and there was no emotion involved except curiosity and a desire to get better. I presume this is the case with almost any team.