Read about a week ago an interesting article challenging Pair Programming
I have to admit the first time I read it it seemed really devastating to pair programming. I however re-read it yesterday when James Nugent sent it by the second time. This time reading through I picked up on something I didn’t the first time.
Table 1 is extracted from a pair-programming calculator developed by the author. It allows researchers to input a number of variables including staff compensation, application size in lines of code, and coding speeds for both pairs and individual programmers. Table 1 shows a typical pattern for average pairs and average individual programmers for 1000 code statements
All of the numbers in the paper aren’t actual research! They are assumptions of the author that were then plugged into a “pair programming calculator”. Which as Mark Nijhof pointed out should “really have more than one author”.
In other words even though its on a “research” site and appears professional its just an opinion piece with made up statistics 😦
I personally think sometimes pairing is good and sometimes its not. I think the bigger question is getting into a more formal discussion of when it is good or not.