Originally posted by Bob Fred:
Two people are pair programming and they disagree about something significant. Does the methodology have a defined mechanism to resolve the issue.
Is this a trick question?
Pair Programming is not about mechanisms, it's about collaboration.
I thought if I was working with the chief architect of the project, we'd do it his way.
If you do this because he has more experience and you wonder wether he might be right, so you want to learn from him by trying his solutin - it might be a good choice.
If you do this because he is the chief architect, it is one of the worst...
If I was working with a green been, we would discuss it longer.
OK.
If no resolution was achieved, we would let management decide the issue.
In hind sight maybe this solution could dump a lot of issues on management they do not want to deal with.
And probably also can't - they don't know the code as well as you do, do they?
Some additional suggestions:
- ask some other team members
- try it both ways, then decide which you like better
- flip a coin (seriously - we once did this, and it worked very well)
All these are suggestions - some might work for you and you have to find out for yourself which ones do. There are no predefined "mechanics".