|
Dude22 wrote: Both parties need to check their egos at the door.
You make it sound more like social engineering rather than software engineering.
The best developers do have big egos and big, inventive ideas. This system restricts it and the best developers leave to find alternative employment.
And yes, I have seen it happen. These guys like ownership of their projects. They don't want to be part of the collective. It's not farming (or the Borg).
Anyway, with more developers working from home and team sizes being restricted, I doubt that this concept will progress much further than large corporations and public services.
Hope this has gone some way to reducing your amazement.
|
|
|
|
|
sirius-black wrote: The best developers do have big egos
Bull.
Jeremy Falcon
|
|
|
|
|
It's not that we are not aware of the benefits. Most of the time I work alone. If I have a C++ problem I can ask the others, but there are things only I can do (Ada wrappers, Fortran repair, etc). When we find an area where we overlap, we can program in twos or threes and it really is so much better, quicker and more fun.
------------------<;,><-------------------
|
|
|
|
|
How many programmers does it take to program a pear. 
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
|
|
|
|
|
Bah! When I was a kid we had to make clockwork oranges!
|
|
|
|
|
Rotten oldtimer... When I was a kid, it was my job around the house to wind those damned clockwork oranges every morning before breakfast.
Will Rogers never met me.
|
|
|
|
|
I shall warn that the term is kind of confusing for non native English speakers like me specially if they aren't familiar with development methodologies. It sounds like working with someone else on a project. I doubt that, without description, results of this survey are accurate.
Anyway, to me pair programming is not worth distractions specially when interrupted at the middle of implementing an algorithm in mind.
"I hope you live a life you're proud of. If you find that you're not, I hope you have the strength to start all over again." - I wish I knew who is this quote from
modified on Monday, September 27, 2010 2:59 PM
|
|
|
|
|
Um, you are NOT confused, and you are correct in your assumption... IT DOES mean working with someone else on a project.
Hamed Mosavi wrote: is not worth distractions specially when interrupted at the middle of implementing an algorithm in mind
In reality the idea is that it is NOT considered an interruption but a collaboration where the two people work together at the same time to achieve a goal. One codes, the other helps think, design, and provide feedback.
I have done it, and at times it works well, at times it does not.
As with most 'methodologies' I don't think there is ONE answer to all problems.
If there were, we would not have as many choices as we do right now 
|
|
|
|
|
Ray Cassick wrote: IT DOES mean working with someone else on a project
Obviously I was unable to express myself clearly. Sorry. My bad. Need to work more on my speaking skills.
Normally in our team, we co-work on two different machines. We have the same source repository but we think separately. The very first time I heard the term Pair Programming, I thought it's about this type of coding in contrast to developing a whole software alone; a standalone developer. Here comes the ambiguity for some of us.
I like what is said here[^].
I've done it for one such scenario and I think it works. So yes you are absolutely correct that at times it works well. Also correct that I don't think there is ONE answer to all problems.
But honestly I think everyone does it automatically in such situations. What I am referring to as horrible is when I code and someone not understanding what I'm doing yelling at me why I'm doing it.
I agree that in a team collaboration is very important, but I believe it's better to be done at design time not coding time. Anyway it's just my opinion and your mileage might vary.
"I hope you live a life you're proud of. If you find that you're not, I hope you have the strength to start all over again."
- I wish I knew who is this quote from
|
|
|
|
|
No! Not that!
You fool! The loops DECRIMENTING! Rename that variable!
Much more fun. 
Panic, Chaos, Destruction.
My work here is done.
or "Drink. Get drunk. Fall over." - P O'H
|
|
|
|
|
... with mixed results.
Some people just can't work if someone is sitting behind them and others enjoy working together with others. If you can pair two people from the latter category, the benefits are obvious: exchange of knowledge, more focus (less time spent on CodeProject  ), no need for code reviews. Than again, most programmers fall into the former category, and forcing them to work with others will lead nowhere.
As Jim Morrison used to sing: People are Strange[^]
|
|
|
|
|
Nemanja Trifunovic wrote: Some people just can't work if someone is sitting behind them
I can not type when someone is standing next to me. Well I have way more mistakes.
John
|
|
|
|
|
John M. Drescher wrote: I can not type when someone is standing next to me. Well I have way more mistakes.
One of the brightest junior developers I ever hired was like that. I gave him a task and sat with him to help him find his way around in the code base, and he started making typos and became visibly nervous. Then I left him alone and told him to just ask if he needs any help from me, and everything went fine from that point on.
|
|
|
|
|
I tried it a couple of times and it worked very well.
Normally I hate having someone looking over my shoulder.
Somehow discussing a problem together did not seem like looking over my shoulder.
Also, a bit of light banter whilst getting started goes long way.
|
|
|
|
|
Sometimes we do some pair debugging if figuring out something is taking too long.
Two resources for the new piece of fresh code I see it as a waist, prefer putting that extra brain on a testing/deployment "team".
|
|
|
|
|
Never really worked with debugging code either. Just too many different ways of doing things and of course my way is better and faster (for me).
|
|
|
|
|
In the 80's, a physicist and I used to play Swords of Glass together: one to map, the other to move the characters.
This was extended through the Might and Magic series, at least through the World of Xene
I'm just not sure if this counts.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek dissappointment. If you are searching for perfection in yourself, then you seek failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
. . . Don't Tell . .
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek dissappointment. If you are searching for perfection in yourself, then you seek failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I remember pair programming with a good looking woman. That was over 20 years ago. But back then my programs were 500 lines max. Now I average 75000 line programs written entirely by me. Pairing up would only slow down the works..
John
|
|
|
|
|
John M. Drescher wrote: I remember pair programming with a good looking woman.
Oh, yeah, there was that LISP class in college...
|
|
|
|
|
I often used "Pair programming" in a very broad way when I was in school and we had to work has a team. The team was small and the project scale made configuration management irrevalent. Therefore, it was simpler to do pair programming and share our knowledge.
|
|
|
|
|
I'm part of a team of a dozen people developing a product. A lot of our testing and debugging is done with several of us together at once. It's pretty effective for us.
As far as "pair programming[^]" goes under the formal definition, HELL NO!
|
|
|
|
|
|
When implementing complex algorithm
Life's Like a mirror. Smile at it & it smiles back at you.- P Pilgrim
So Smile Please
|
|
|
|
|
Which we do from time to time.
Pair coding is extremely rare.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
