Posted: Mon Sep 19, 2005 8:13 am
Realtime comments, no doubt are an invaluable resource, I'm more concerened about two or more people updating the actual code at the same time 
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
Yeah, ideas/programs are like birds, catch them while they are there or else they get too far away and we have to work hard to get them back.feyd wrote:when a computer isn't directly available, I've written plenty of code on a piece of paper/napkin/skin
Like I said above, it all depends on the person. Some people really thrive on Pair Programming, and for them, its definitely NOT a poor use. Its a fantastic method for reducing overall error count and improving quality. Saibot mentions that it <span style='color:blue' title='I'm naughty, are you naughty?'>smurf</span> him off. That happens because someone found a problem - a problem that is there whether someone else noticed it or not. Less errors = better quality = a good use of HR.Grim... wrote:And it's got to be a poor use of Human Resources, surely?
Oh, such a horrible thought.Grim... wrote:(But thank God you don't get a Clippit trying to help"It looks like you are coding a loop. Do you want some help?")
But the thing is, it works when the person at your side is on level with you, maybe a senior also and there exists a good understanding between both. When such conditions are not met, Pair Programming really does become a nightmare. We have tried such thing and believe me we were more than satisfied with the results. But with some/many of the team members, there exist some issues like,Roja wrote:Saibot mentions that it <span style='color:blue' title='I'm naughty, are you naughty?'>smurf</span> him off. That happens because someone found a problem - a problem that is there whether someone else noticed it or not.
This is what I believe Pair Programming really is... both concentrate on same piece/block of code at a time with one person coding while other reviewing it, not two different parts of fileJenk wrote:Pair Programming is not two (or more) people editing the same file, at the same time from different terminals. It is two people working together, usually from the same terminal, with only one person editing the file. (Think Pilot and Co-Pilot)
This is the first I have heard of pair programming except when you have a new programmer on board and you want to get him/her up to speed quickly. I would still think this is slower then having the programmers work on two different modules. Even though you might find more bugs with pair programming, much of the dev work done in UAT/Testing comes from the client asking for small changes which are technically not bugs.But the thing is, it works when the person at your side is on level with you, maybe a senior also and there exists a good understanding between both. When such conditions are not met, Pair Programming really does become a nightmare. We have tried such thing and believe me we were more than satisfied with the results. But with some/many of the team members, there exist some issues like,