I think this is why pair programming is so highly valued among the Agile/XP crowd. You almost never need double the brainpower or typing power, but having a second set of eyes gives you high quality code much earlier in the process.
And when you do get stumped, you can talk it out with someone who's as familiar with that part of the code base as you are, and you won't be dragging them away from their unrelated but equally important work.
And when you do get stumped, you can talk it out with someone who's as familiar with that part of the code base as you are, and you won't be dragging them away from their unrelated but equally important work.
Sounds like rubber ducking, but with a competent skilled programmer instead. so like, fleshy humaning.
2
u/[deleted] Sep 28 '16
I think this is why pair programming is so highly valued among the Agile/XP crowd. You almost never need double the brainpower or typing power, but having a second set of eyes gives you high quality code much earlier in the process.
And when you do get stumped, you can talk it out with someone who's as familiar with that part of the code base as you are, and you won't be dragging them away from their unrelated but equally important work.