21–30 of 121 posts
It's the environment that actively sabotage such way of working, or attempts to mandate it as a ritualistic practice, that is unnatural.
A natural extension of two people in front of a whiteboard, nothing more.
A lot of dev teams suffer from the iamverysmart problem already, and PP just seems like a way to exacerbate it.
If forced to choose between pair programming and not programming at all, I think I would choose the latter.
Why?
Some of my best and most important projects have started out as terrible diversions that after a while even I begin to wonder if I shouldn't be doing it.
Earlier quoted context omitted.
Not OP, but for me, it's like having someone stand over my head with a pot, banging it with a spoon incessantly. It utterly destroys my ability to concentrate. Had a chance to closely observe a session once. Looked through the code later--total garbage. Apparently it works for some, but you couldn't pay me to do it. (Also, seems unfair to programmers that can't hear well or need other accommodations.)
Were you coding with someone either much more, or much less experienced than you? Without knowing the case, this could affect how successful the pair coding is.
When the design is ready I want to present it to people and they have to prove to me that I produced crap. If they do I am back to a drawing board . If not (and that became the most often outcome after few years in the industry) then f.. off leave me alone and I'will put my design into a code. The last thing I need at this point is someone breathing down my neck.
After the code is finished and I am reasonably happy with it I would like me some code review if condition allow. Not very often as I mostly work either on my own products and do not have people around for code review and/or making some extra dosh doing the same thing as consultant and consultants do not often get this luxury.
All in all I can see no benefits at all in doing pair programming for myself. If someone is happy with it and their boss lets them do it then sure, go full monty. Just please do not force this style on people. Not everyone can tolerate close contact for extended time.
If forced to choose between pair programming and not programming at all, I think I would choose the latter.
Why?
Frequent peer review and collaboration on important architectural decisions is sufficient. Sitting down and actually writing code together is unnecessary torture.
Imagine some legendary coder like Linus Torvalds or John Carmack writing the Linux Kernel or the Quake engine side by side with another dude at their keyboard all day every day. It's a fucking absurd and infantile concept.
Earlier quoted context omitted.
Not OP, but for me, it's like having someone stand over my head with a pot, banging it with a spoon incessantly. It utterly destroys my ability to concentrate. Had a chance to closely observe a session once. Looked through the code later--total garbage. Apparently it works for some, but you couldn't pay me to do it. (Also, seems unfair to programmers that can't hear well or need other accommodations.)
Pairing programming is like any skill. If you never do it, you will be terrible at it. I also believe that pair programming requires a level of psychological safety that not all orgs possess.
Earlier quoted context omitted.
Were you coding with someone either much more, or much less experienced than you? Without knowing the case, this could affect how successful the pair coding is.
Two people somewhat less experienced. I don't believe that was the issue.
I read through this quickly, but I couldn't find any mention of pair programming not being suitable for sensitive and introverted people - especially those that suffer from anxiety and other mental illnesses that can be made worse by the stress of pair programming. Whilst the article mentions that it "can be hard and stressful" there is still the assumption that most people are more or less the same in terms of menta…
It sounds like you and I are very similar. I was part of a company that went down the road of XP...it was very difficult for the first 6 months but it changed my life. I am much different now than when I started (I am actually in a role where communication is a big part of my role)...I forced myself to stick it out. Not going to lie there were a lot of tough moments on long train-rides home but I not only learned a t…
I'm still not convinced that it would be good for my wellbeing and happiness, given that I've experienced PP for a couple of weeks on and off (not anywhere near 6 months like you!).
I do like to collaborate with co-workers to solve problems, for sure, and we will often share screens and benefit from putting our minds together. But PP for 6 ... 8 hours a day, without periods of quiet contemplation, spent with my own thoughts? When I think about it like that, my heart sinks.
If anyone is hiring I'll apply.