> I'd prefer pair programming to be something done to create new code, not just to get past a problem.
Honestly, I couldn't agree more. I struggled with the title, because I see pair programming and helping someone overcome as two different things.
The reason I went with the title is because many people I know see it as pair programming and it could gain some more traction because of it. (most of them aren't deep into XP practices).
How will your answer be different if your colleague asks questions rather than you making a head start?
I wonder if the issue here is XY problem, situations where the question is about the attempted solution (Y) rather than the root problem itself (X). You could pause once you explain the problem before going into a solution.
This is something I've tried working on lately and I realized it for the same reason. I let the other person come at it with a fresh perspective and see what they think about and what questions they ask.
Interesting perspective Tiger.
Two thoughts:
I'd prefer pair programming to be something done to create new code, not just to get past a problem.
Rubber ducking works - where you do just 'rant' (share) the issue. Maybe this is the step post Rubber Duck?
> I'd prefer pair programming to be something done to create new code, not just to get past a problem.
Honestly, I couldn't agree more. I struggled with the title, because I see pair programming and helping someone overcome as two different things.
The reason I went with the title is because many people I know see it as pair programming and it could gain some more traction because of it. (most of them aren't deep into XP practices).
I got a post on Rubber ducking actually haha :D
Stay tuned!!
Great reflection, Tiger!
How will your answer be different if your colleague asks questions rather than you making a head start?
I wonder if the issue here is XY problem, situations where the question is about the attempted solution (Y) rather than the root problem itself (X). You could pause once you explain the problem before going into a solution.
Very true, Tiger. Great, actionable tip.
This is something I've tried working on lately and I realized it for the same reason. I let the other person come at it with a fresh perspective and see what they think about and what questions they ask.
100% :D