Page 2 of 2

Posted: Mon Sep 19, 2005 8:13 am
by Jenk
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 :)

Posted: Mon Sep 19, 2005 8:14 am
by n00b Saibot
feyd wrote:when a computer isn't directly available, I've written plenty of code on a piece of paper/napkin/skin :)
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.

Posted: Mon Sep 19, 2005 8:20 am
by Roja
Grim... wrote:And it's got to be a poor use of Human Resources, surely?
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.

However, if you are on the other side of the coin, where PP is just painful, its a waste.. you get bitter, you slowdown, and you can't think clearly. Thats bad.

Thats why its important to remember that every person is different. I know some people on these forums MUST have syntax highlighting and code collapsing in their editor. I would rip my eyes out if I had those in mine. Every person has different things that works for them. There is no one right way to do things. :)

I think we are way off-topic now though.. we answered the OP's question, and should just move on to other threads. :P
Grim... wrote:(But thank God you don't get a Clippit trying to help :lol: "It looks like you are coding a loop. Do you want some help?")
Oh, such a horrible thought.

("It looks like you are improperly using the Row-Iterator Pattern. Would you like me to help you implement it correctly?"). EEEK!

Posted: Mon Sep 19, 2005 8:32 am
by Grim...
Unless, of course, you were using the Row-Iterator Pattern wrong, and it implememted it perfectly...

Ah... We can dream...

Posted: Tue Sep 20, 2005 3:45 am
by Jenk
Just to clarify, as there has been some confusion (on my part)

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)

:)

I've been doing the above for years, hence my confusion at this "New Concept" of Pair Programming :)

Posted: Tue Sep 20, 2005 4:18 am
by n00b Saibot
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.
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,

1. Code-Ownership - We have a pre-concieved notion that Code-Ownership improves code quality since an individual's prestige is at stake. this notion is difficult to break in some cases.

2. Ego Clashes - Each person has some amount of ego which he doesn't want anyone to step on. these clashes adversely affect the environment and productivity both, and also kill the team spirit as a whole.

3. Lack of Self-Confidence - One may or may not feel confident in working while you know that another person is watching very piece of your code and lack of confidence may lead to committing many errors which he would not have done in presence of his confidence. I agree that peer-review is definitely a good thing but it should not be a forced one. :wink:
Jenk 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 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 file :!:

Posted: Wed Sep 21, 2005 12:25 pm
by alvinphp
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,
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.