I've done it in Google hangouts but I only shared my IDE. And I reduced the size of the IDE window a bit so that it was large and clear on my co-worker's screen

I've done it in Google hangouts but I only shared my IDE. And I reduced the size of the IDE window a bit so that it was large and clear on my co-worker's screen. The way we did it, I had the keyboard all the time, so when he wanted something to be typed, he told me. Or, we would work on two different files, i.e. the kind of change that cascades across several classes, and since we were working on an SVN branch, we frequently committed to share the work to date. It is a different kind of pairing than the single PC with two keyboards and two mice, but it worked well enough to get two pairs of eyes working on one set of code. With two PCs it was easier for one person to drop into a browser to do research while the other was still looking at the shared IDE and thinking about the next move. I have used a tablet to do research while doing single PC pairing but it was actually more awkward than the remote pairing. And if there is enough timezone difference you can relay the work by doing handovers at the beginning of your colleague's workday.