Originally posted by Avijeet Dash:
I guess, the idea is one person codes and thinks about the syntax, logic etc. and the other person watches to see any spelling errros, and think fast and do a pre compilation in mind to see wheather the code with compile and run or not.
so the 2 people will keep talking, discussing and coding.
You contradicted yourself and confused me again...
You say "...one person coding..." at one place, and then "...2 people talking... coding." at another? Is it one person writing his own code and checking the logic of the partner's code? In that they are working on different modules/methods.
The positive part of it is you don't get bored of coding alone. And If you like your companion, life is great. In a movie kind of plot the programmers can get married and have a great career.
Hmm... just heard yesterday that Narayanmurthy's wife (INFOSYS founders) used to type the code for him. What a timely example of pair-programming
Sanjeev
Originally posted by Avijeet Dash:
I guess, the idea is one person codes and thinks about the syntax, logic etc. and the other person watches to see any spelling errros, and think fast and do a pre compilation in mind to see wheather the code with compile and run or not.
Originally posted by JUNILU LACAR:
Nooooo... it goes much deeper than watching for spelling errors and syntax.
The second person's (the one not "driving") role is that of a navigator. He has the high-level view of things, thinking more strategically/tactically. The person driving focuses on the programming mechanics. True, the navigator may notice a spelling error or two or suggest a better name, but he/she is really more focused on things like thinking of ways to test, ways in which the current direction the design is taking will affect future flexibility, and making sure that the driver doesn't go on to any sideroads that don't address the current problem at hand. The navigator also may watch for opportunities to refactor which the driver may not immediately see. IOW, the navigator tries to keep the driver focused with respect to the bigger picture and the task at hand.
Then, if the driver gets stuck, they can switch roles.
Junilu
Originally posted by shailesh sonavadekar:
Sanjeev , I think there is a lot of discussion about this in " Process Forum ". Pleas see the various threads in that forum.
I think this topic can be best discussed in that forum.
Plus , you are reading Kent Beck's book. you will get good info. in that.
Your Friendly Bartender
Shailesh.
Originally posted by Shailesh Sonavadekar:
Sandeep , Process is the topic which is very difficult. How many people working in s/w industry are aware of the things like S/w engineering. How many organisations are having processes ? What is the real meaning of Process ? There are many such probing questions.
Originally posted by shailesh sonavadekar:
I think Sir Paul Wheaton has given sufficient thought to keep OOPS & Process Forum separate. In Process Forum , we are not only discussing XP , but other processes also. It will be better to keep separate forum for them separate so that discussion can be more focussed.
Thank you for your suggesstion. I will definitely ask Paul Wheaton about this. But , my viewpoint is to keep them separate.
What other guys think ? Good or bad ?
Your Friendly Bartender
Shailesh.
The fastest and most reliable components of any system are those that are not there. Tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
|