Comments on: Pair Programming vs. Code Reviews – It’s a no Brainer

By: Stefan Reuter

Stefan Reuter — Tue, 30 Nov 1999 00:00:00 +0000

Could you provide some more insights on how you do pair programming over a remote connection?
We do some pair programming but only with people at the same location which leads to some kind of “site-local knowledge”.

By: Greg Wilson

Greg Wilson — Tue, 30 Nov 1999 00:00:00 +0000

1. Is the “15%” a comparison of pair vs. review, or pair vs. solo?
2. Is there independent validation of any of the other claims (spreading the knowledge, raising skills levels, etc.)?

By: Mark Levison

Mark Levison — Tue, 30 Nov 1999 00:00:00 +0000

Stefan: pairing over a remote connection – I use Real VNC (or any other VNC). The other developer can see my machine and has much control as I do. Caveat Emptor – this is huge security risk, don’t run the server when you don’t need it. Only run it over an internal network or VPN, ….

BTW its not like the real thing. Nonetheless if you’re not sitting together its better than a boot to the head.

Greg: I don’t know much about the details of the study. The other claims are merely based on mine and other’s experience. As I recall you’re a prof – you have students maybe you could run experiements on them. I must admit I tend not to look for formal proofs in a case like this. I tried it for a while, discovered it works and wouldn’t go back.

I challenge anyone – try it for six weeks and see if you would go back afterwards.

By: Steve Howell

Steve Howell — Tue, 30 Nov 1999 00:00:00 +0000

As you say, pair programming happens in real time.

My biggest problem with static code reviews is that they happen way too late. I’ve been in code reviews where people make perceptive comments about the design, but the code is already in QA, so there’s nothing you can do about it. Even on the other end of the spectrum, where people just want aesthetic improvements to the code, there’s a reluctance to actually implement the changes.

If pair programming is not an option, then I would schedule code reviews for halfway through the implementation, even if that means the final code doesn’t get reviewed. At least then the code review could help steer some of the implementation in a meaningful way.