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.

Here at Collective Idea, we do a lot of pair programming. We also believe in remote working. When pairing with any of our remote developers, we typically use a combination of SSH and tmux. There are a lot of good articles on this type of setup, but we've settled on an easy solution that works well.

Relevance posted some notes on remote pair programming so here are ours too.