Originally posted by George Harris:
I found partner pairing a terrible mistake when the task is easier. It turns into a nagging session with one of the programmers insisting that the other type faster.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Payam Fard:
How does pair-programming work?
Does it really make sense to have two developers' time on every single line of code? I agree that the code would be reviewed by two developers at the development time and also the developed code would include the thought process of two developers, but they could be producing twice the code if they code separately given well-designed system!
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by lechon manok:
I agree with Ilja, the thinking part is critical - two heads are definitely better than one. This to me is the most important benefit of pair programing.
It would also be interesting to know if any social or personality issues come into play. How well does a developer with a "lone wolf" personality adapt to pair programming?
What if contrasting personalities make it very difficult to work together?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Ilja in another thread:
Well, *there are* crossplatform solutions for this - for example there is an eclipse plugin for pair programming: http://sangam.sourceforge.net
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Awais Bajwa:
May i know that is there any relation between Extreem Programming and Pair Programing?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Ilja Preuss:
Well, it *can* be very interesting and productive. If it isn't, they probably find other coworkers to pair with. Again, it seems to be a broader team issue to me, needing to be resolved anyway...
Live Free, Live Happy
Originally posted by Laurent Duperval:
My experience has been that very seasoned developers and very green developers make for difficult pairings. The ideal pairings I have foudn are senior-senior, senior-intermediate and intermediate-junior. senior-junior pairings tend to intimidate the junior and tend to frustrate the senior. intermediate-intermediate may lead to slower learning. But that last one, I'm not sure about.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
My experience has been that very seasoned developers and very green developers make for difficult pairings. The ideal pairings I have foudn are senior-senior, senior-intermediate and intermediate-junior. senior-junior pairings tend to intimidate the junior and tend to frustrate the senior. intermediate-intermediate may lead to slower learning. But that last one, I'm not sure about.
Originally posted by Rajeev:
Pair programming in XP works only if Personal Egos do not interfere woth work. I have found lot more egos in Software engineering than any other field. [..] My Experience has found pair programming as defined in XP very unproductive on everyday programming. What I found working is code review with a peer and also on bug tracking.
Books: Pragmatic Unit Testing in Java, Agile Java, Modern C++ Programming with TDD, Essential Java Style, Agile in a Flash. Contributor, Clean Code.
Originally posted by Jeff Langr:
I enjoy pairing: I know that I don't have all the answers
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]