You might want to read up on agile methodologies.
These are not programming languages but are ways of working on a programming project and as well as being widely recognised as working quite well, they more often than not encourage working in a team.
For example "extreme programming" has nothing to do with base jumping whilst writing C++ and a lot to do with working in pairs.
You won't regret learning these things as they will help you work on a programming project in a team with others who already work by these concepts.
Keep away from scrum though as it is more suited to working closely in an office environment as it encourages regular face to face meetings.
Good luck!
Erh... while I am all for agile methods, I thought that XP had died a horrible death in the many "work trainwrecks" it caused many moons ago.
Whoever thought sitting two persons at one screen, and getting anything than REDUCED efficiency for double the wage should be shot, and then shot again.
On a more serious note, are there ANY newer scientific studies that prove that extreme programming does work as advertised, even if certainly not as well as the original authors believed?
My point it: you are basically preventing one guy from working flat out (he lacks his own machine), while disturbing the other guy in his work (while having another pair of eyes can be benefical at times, programming normally is nothing where constant distractions by another person is good).
Give both a machine, let them work alone, and instead do regular code reviews and meetings. You still get part of the "additional pair of eyes" advantage, while giving each programmer at least half a day of undisturbed work time instead of both constantly a) fighting for the steering wheel, b) fighting over coding standarts and implementation details, c) interrupting each other while implementing complex parts because of some minor ommissions ("you forgot to put a comment there", "your indentations suck").
Lets not get into how much strain it is on a work relationship when you constantly have someone breath down your neck, while you are trying to get work done. Even the most social programmer will get fed up of having to sit next to the other guy for many hours every day.
Office warfare certainly will get dead serious quickly
On the other hand, I heard many advocating using PARTS of Scrum even as a lone wolf of small team. While many practices certainly are meant to facilate managing the team with the least amount of overhead (15 minute standup meetings instead of 1 hour scheduled meetings where people get comfortable and chit chat for 1.5 hours - yes PLEASE!), some can be used for self management.
Kanbaan Boards and all....