4 ms·
Yes, it is my experience too that pair programming works best when you both are at roughly equal levels of experience and both really want to succeed with the t
by osivertsson 15y ago
Yes, it is my experience too that pair programming works best when you both are at roughly equal levels of experience and both really want to succeed with the task at hand.
Code reviews in groups often work really good despite different levels of experience though.
It is exhausting to do pair programming, but when it really does work the feeling of progress and mutual knowledge sharing is awesome. In these optimal cases me and my coworkers have worked in pairs for 5-6 hours per day. Pushing on for longer would not have gained anything, rather the opposite.
- AlisdairO 15y agoIn support of pair programming with a knowledge disparity, I have to say I've found it a fantastic way of bringing new team members up to speed. Yes, it's a bit of a pain in that it can bring productivity down for a while, but I really feel that it has long-term benefits.
- mtts 15y agoI work with a lot of interns these days, doing what's essentially pair programming with them and I don't feel their lack of expertise brings me down at all. Instead, I find having to explain everything I do to them brings a clarity to my own mind that is difficult to obtain otherwise. Of course it does help that when my explanations truly fail, I still have the nuclear option (Hey, they pay me to teach you this stuff, so just believe me) available, but (I'd like to think) I only rarely use it.
- MaysonL 15y agoMy experience is that pair programming works almost as well when one of the pair is virtual, or time-shifted [i.e.: code review or review rehearsal]. And it's much more efficient.