The Pitfalls and Perils of Pair Programming

The concept of pair programming first became well-liked thanks to "extreme programming" or XP--a set of practices that supposedly allows companies to manufacture software in a more efficient, more "agile" manner. Proponents of XP claim that it allows programmers to reply to shifting or ambiguous software requirements without sacrificing quality. Skeptics disagree, arguing that these alleged assistance are either illusory or exaggerated. https://agaviworld.com/

XP proponents argue that two programming heads are greater than before than one--that two software developers effective together will tend to fabricate better, more honorable and more maintainable than a single programmer committed alone. This practice is known as pair programming, and at first glance, it sounds like a great idea. Personally though, I think that it smacks of a "one size fits all" mentality. That is, it assumes that two programmers committed in concert will indeed be more efficient and that they will produce better results. I think there is good reason to agree to otherwise.

The much vaunted Williams study

XP fans typically dwindling to an infamous testing headed by Prof. Laurie Williams at the college circles of Utah. In this study, Williams concluded that pair programming takes 15% more epoch than solo development, but results in software that is 15% better. They argue that this modest growth in progress mature is a little price to pay, previously enlarged code mood means that less become old and effort will be required forward-thinking all along the road - during breakdown and maintenance, for example.

I think that there are numerous problems subsequent to this study, though. How did the researchers gauge software quality, for example? The used the length of code as the environment metric; that is, the shorter the source code, the greater than before they deemed it to be. The reported, "The paired teams consistently implemented the thesame functionality as the individuals in fewer lines of code. We agree to this is an indication that the pairs had bigger designs." I think this is a rushed leap of logic, to tell the least!

Does shorter source code exhibit greater quality? Sometimes, perhaps. However, one could just as easily speculate that the longer code contains more bug fixes and safeguards. In addition, calculation more code lines - to embrace a design pattern, for example - can create the software more efficient or easier to maintain. I think that the presumed correlation amid code length and nonexistence of vibes is not a hundred percent justified at best.

The psychotherapy also exhibited a rude act of participant bias. The students in a class were asked if they preferred to achievement in groups or alone. 35 of the respondents said that they preferred collaborative working; of these students, 28 of them were prearranged to constitute the pair programming experimental group. The steadfast seven were placed in the solo programming group, i.e. the experimental controls. This created a strong experimental bias; every of the pair programmers were amenable volunteers, whereas some members of the manage work were there reluctantly.