{"id":2329,"date":"2019-12-02T09:33:19","date_gmt":"2019-12-02T07:33:19","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=2329"},"modified":"2020-01-14T18:27:48","modified_gmt":"2020-01-14T16:27:48","slug":"how-to-remote-pair-programming","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2019\/12\/how-to-remote-pair-programming\/","title":{"rendered":"How to: Remote Pair Programming"},"content":{"rendered":"\n

Before getting into remote pair programming, let’s see what pair programming is.<\/p>\n\n\n\n

Pair programming<\/h2>\n\n\n\n

Pair programming is when two programmers write code on the same requirements \/ problem. There are two roles: driver and navigator. The driver has the keyboard and writes the code. The driver focuses on short term implementation. The navigator looks at long term strategic decisions and double checks the driver’s implementation details.<\/p>\n\n\n\n

In many cases pair programming is a lot more efficient, the code being clearer, nicer and with fewer defects. Nevertheless pair programming can be tiring, especially when doing it for the first time. <\/p>\n\n\n\n

As a rule of thumb, you don’t need to pair the whole day, because it’s tiring, difficult and sometimes inefficient. Choose more complex, difficult or areas less known when doing pair programming.<\/p>\n\n\n\n

Remote pair programming<\/h2>\n\n\n\n

Not everyone is at the office all the time. Sometimes we work from home, or we are in another office. So it’s a good idea to use this useful tool of pair programming also when you are not next to the other programmer. We call that remote pair programming.<\/p>\n\n\n\n

\"Remote<\/figure>\n\n\n\n\n\n\n\n

Infrastructure<\/h2>\n\n\n\n

You need:<\/p>\n\n\n\n