In the last part of our four-part series, we look at a variety of roles one can take on during a pair programming session. Are you the researcher, tester, sounding board, or something else?
Pair programming isn’t always just about working with another person. Sometimes, partnering up on a project requires you to know more about how YOU work within the partnership.
Part two of our four-part series on pair programming touches on the topics of the time involved when pairing, why you should keep your ego in check, and how to assume the best of your pair partner.
So what can you, as a well-meaning professional developer do to contribute more to your team? We have several suggestions for reaching your pair programming potential.
Relevance posted some notes on remote pair programming so here are ours too.