Comments on: Episode 54: Code Review

By: Jade Robbins

Jade Robbins — Thu, 30 Dec 2010 16:48:31 +0000

@Ruthie: Very difficult to do. Just make sure you have clear statements of the benefits and perhaps some scientific studies if you can. Also asking for just some time to try it, say 6 months, and then re-evaluating it with management could be beneficial.

By: Ruthie Copeland

Ruthie Copeland — Fri, 24 Dec 2010 01:00:22 +0000

We have kicked around pair programming but we can’t get upper management to buy off on it.

By: Eric Wendelin

Eric Wendelin — Tue, 16 Feb 2010 16:18:53 +0000

I can’t agree with coders’ emotions about their code. Personally, I generally hate code I’ve written after a short time.

Good programmers realize that their code is all crap.

By: Jade Robbins

Jade Robbins — Thu, 04 Feb 2010 22:27:54 +0000

That is a bummer, we find that it is pretty effective here!

By: Brian

Brian — Thu, 04 Feb 2010 15:25:48 +0000

We have kicked around pair programming but we can’t get upper management to buy off on it.

By: Jade Robbins

Jade Robbins — Tue, 02 Feb 2010 17:37:46 +0000

@Jeff, so does google do a formal code review process? Distributed snippets? I’m very curious what the work flow is.

By: Jeff S

Jeff S — Tue, 02 Feb 2010 17:33:41 +0000

“Google requires code review for any change to company code or configuration files; there are a few exceptions, but those are subject to review after deployment.”

– http://lwn.net/Articles/359489/