It doesn't have to be all day! (Score 1)

In my most recent contract I've been working with various levels of experience and switch between working solo, teaming with an associate at the same workstation and working remotely on several junior associates workstations. For those that are significantly less experienced I've found that remotely accessing their desktop to demonstrate or help with a problem/question to be very useful, plus I can help more people in a shorter time. I get to continue working on my assignments at a steady pace and they can still work at their own pace. For more the more experienced, it just saved us time, and a long walk (although we all could use the walking!). Either way it was good because we could all maintain our own personal spaces, weren't so constrained by other people's schedules and didn't have to change contexts. While the other was testing a routine or some other long process, I could review documentation or even continue working on my assignment. Team programming doesn't have to be always at the same workstation all the time.