Summary

In this final chapter, we discussed how to make remote access both enjoyable and reliable for your remote pair programming sessions.

While a remote access tool needs to have certain characteristics to make our lives easier and to enable almost seamless remote work, it also needs to have certain security features that keep us safe from harm. It's not just about the tools that we use for remote access but also about all the tools that we use for remote pair programming. All our tools need to have a high-security performance, and we need to continuously audit them and improve their security as much as possible.

Remote access, in one way or another (just the code, or desktop sharing), is essential for remote pair programming. However, opening your desktop and your code on a remote communication tunnel is a risk that we need to take into account. Learn about how your tools and systems work, what the possible risks and threats are, and treat them with diligence and responsibility...