What is Remote Collaboration?

Remote collaboration is a means by which team members separated by distance can collaborate, working toward a single goal. Made possible by various technological tools, remote collaboration has changed the face of business as we see it today by increasing productivity and efficiency.

Why Use Remote Collaboration?

Through remote collaboration digital interfaces, a CEO of a company in one part of the world can work with a CEO of a sister company on the opposite side of the world.

The benefits of this type of teamwork are many and include::

Improved Productivity

According to the Finances Online “Online Collaboration Software Statistics for 2022” collaboration tools can help a 100-employee company to “reach up to $247, 500 in productivity benefits!”

The same source cites a 20-30% increase in productivity for the average business using remote collaboration tools!

Why do th tools improve productivity? Because they reduce lost time by allowing employees to connect regardless of their geographic location!

Access to a Larger Talent Pool

Remote collaboration tools also provide companies with access to a larger talent pool. Rather than being limited to local employees or relocating employees, remote collaboration tools extend the hiring search globally!

A man selecting a male avatar to collaborate with

Access to a More Diverse Talent Pool

Remote collaboration tools do not only increase the pool of potential employees; they also increase the level of diversity within a company. By opening the hiring opportunity globally, a company welcomes the opportunity to bring in more diverse employees who can offer a unique perspective on products, services, and niche markets.

Lower Company Overhead

Remote collaboration tools also allow employees to telecommute, which has proven beneficial during the COVID pandemic. In fact, according to the Finances Online “Online Collaboration Software Statistics for 2022” since the beginning of the COVID-19 pandemic, there has been a 176% increase in collaboration apps installed on enterprise devices! 

The availability of remote collaboration software has saved many businesses from closing their doors during COVID-19, but it has also set the stage for a future more dependent on telecommuting. For many companies, that shift to telecommuting means lower overhead costs as they move away from office spaces and into a more virtual workplace.

Improved Employee Comfort

Remote collaboration also allows employees to work in a home office and establish an environment conducive to productivity. These comforts of home have greatly improved the quality of life for many employees worldwide. In fact, one study (How are millennials shaping the future of work?) even found that “more than 75% of Millennials” now believe that a work-from-anywhere setup or remote work opportunity is an important company policy.

Having an office atmosphere that caters to individual working styles allows employees to cut out unnecessary background noise and distractions. On the same token, employees who work better with background noise can do so without distracting other office workers! 

A woman reading a document with her feet on a desk

Remote Collaboration Tools

As we become a society increasingly dependent on remote collaboration tools, the number of tools at our disposal is growing. Some of these tools include:

Other software options offer all these features in a single software suite, making virtual collaboration options much more diverse; Drovio is one of those software options.

Drovio Remote Collaboration Tool

Drovio is a multifunctional tool that offers a variety of features that are designed specifically for remote collaboration regardless of the distance between users.

Security

One feature that is a necessity for any remote collaboration tool – no matter how big or small a company is – is security. Through P2P technology and end-to-end encryption of each session, every step of using Drovio is a secure experience, so you never have to worry about data leaks or compromised corporate secrets. 

Low Latency

Drovio also boasts low latency, meaning that users get a real time experience when collaborating on any applications.

Swap Who Shares

Drovio also has a “swap who shares” feature that allows users to swap between being the presenter and guest. With one click of the “swap” icon, users can choose what they want to share with the other party!

One Click Invites

Drovio’s one-click invite system also makes it seamless to invite users. Your contacts appear on the Drovio and you can start screen sharing sessions with them from one click.

Record Your Session

Drovio’s “Record Your Session” feature is an extra feature that makes it simple to record each Drovio session for future reference. This feature is perfect for onboarding videos and instructional walk-throughs that will need repeating frequently.

Shared Control

Drovio’s shared control feature allows up to ten session users to have a mouse cursor within the shared screen. Giving each participant control over their own cursor makes group discussion and explanation a much easier process!

Voice Chat and Video

Of course, Drovio also offers voice chat and video features that form the base platform of any remote collaboration tool! Drovio lets you join any session from a web browser or the app - unlike some other software options on the market. Users enjoy dual access to Drovio so that the system is usable from any device, no matter where you are!

Other Remote Collaboration Tools

Drovio is not the only remote collaboration tool out there - but with the sheer scalability of service and the number of features it offers, it is worth investigating for your company's needs. 

Conclusion

Remote collaboration tools are available with a range of features from video conference calling to complete remote collaboration software suites like Drovio! These valuable tools enable companies to reap the benefit of remote employees while saving overhead costs and improving overall corporate efficiency. 

Product Update - January 2022

Hey folks, hope you had a great start into 2022! As you know, with new years come new resolutions. Our resolution has been to provide you with fresh news about what we've been up to with Drovio. We'll know do that on a monthly basis via a video. I hope you'll like this new format!

I’m excited today to bring you around our January update. But first, I’d like to thank you for all the feedback you shared with us through our Google form. It’s highly appreciated and valued.

And when you do that, you actually help us shape the future of Drovio. A future aligned to your image, to your needs.

So keep the feedback coming on drovio.com/feedback. We love hearing from our users.

Alright, let’s jump right in and take a look at the cool new things we added to the app.

Share a portion of screen

Sharing a whole screen with your team is great but sometimes you just don’t want to show what’s running on your computer. And let’s not talk about those unsorted screenshots on your desktop. With Drovio, you could already share a specific application. You can now share a static portion of your screen as well. To do that, you just need to select the new option “Share portion of screen” when you’re starting a call. You then get a rectangle selection that you can magnify or shrink. Click share and all the participant interactions get restrained to this portion of screen. If you’re in the middle of a session, you can also quickly switch to this new sharing mode through the session toolbar. A green outline will appear around the apps and portions of screen you share on Drovio. But you can customize that behavior on the app’s preferences.

Mac M1 chips support

You’ve been numerous to ask for a native support of the mac M1 chips. I’m glad to let you know that it’s now available. The binary comes up as a secondary package in beta for the moment. We’re currently working on aligning the app’s dependencies for each OS and architecture. When we’ll roll it out of beta, both previous and new binaries will be packaged as one. If you use brew, we’ve updated the cask so you don’t have to figure out what package you need to download. With the new mac M1 native support in Drovio, we saw CPU usage lowered by up to 10%, thus improving latency as well when sharing dynamic content.

Microsoft Teams integration coming soon

You probably know that we are big fans of Slack. This is one of the coolest tool to communicate with your remote team or even your customers. Our integration lets you jump on a Drovio session right from the Slack app using the phone button and it’s currently featured in the essential apps category of their directory. Today, I’m pumped to announce that we’ll also let you start Drovio sessions right from within Microsoft Teams. This new integration will be available very soon and the experience will be similar to what we provide through Slack.

We hope that you find those new additions useful. Be sure to download the latest version of the Drovio app.

Happy collaborating!

Remote Pair Programming: The Specificities

Using remote pair programming (also known as distributed development) allows developers to collaborate in real time and on the same codebase regardless of their location or physical distance from each other. Remote pair programming provides many benefits over more traditional ways of working, such as reduced overhead costs, improved code quality, better coordination and communication between developers, improved employee satisfaction and retention, and more flexible scheduling options. But remote pair programming can also present some challenges that you’ll need to be aware of if you want your team to reap the benefits without encountering any problems...

What is Remote Pair Programming?

In short, remote pair programming is having two programmers collaborate in real time through one computer. One person writes code while another reads it, giving feedback and tips on how to improve code. Remote pair programming helps you get more work done because it’s less isolating than coding alone. But before we can talk about remote pair programming, let’s first talk about regular pair programming. (Regular pair programming is where two programmers are sitting side-by-side working together to solve a problem.) Regular pairing has many benefits: both people are typing away at their own computers; they’re reviewing each other’s work; they can jump on any problems that pop up; and they can bounce ideas off of each other constantly. There are drawbacks as well—they aren’t necessarily saving time because they have to run back and forth for questions or help; not everyone works best when paired up with someone else all day; some companies don't think its cost effective for every programmer to be paired; etc... If you want to learn more about why pairing is beneficial, check out our article on reasons why pair programming rocks! 

What are the Benefits?

The biggest advantage of remote pair programming is that it greatly expands a team’s flexibility when considering where people work. If an employee has a family emergency, or if they simply want to move closer to relatives, there’s no need for them to relocate; most companies provide laptops and a good internet connection, so employees can stay at home and keep working remotely. Remote workers also typically cost less than in-office employees; they don’t have an office or parking space to pay for. Additionally, many find that they prefer telecommuting—it gives their family a break from interruption and allows them to focus on getting their job done well. There are some disadvantages to telecommuting as well: company culture can be lost, especially if your company relies on day-to-day interactions between coworkers. A pair programming tool like Drovio solves some of these problems! Despite these potential issues, more and more companies are going remote because it allows them to expand without having physical limits—there is no longer a requirement for everyone's office/workplace being co-located.

How Does it Work?

The two developers are connected through a pair programming tool (such as Drovio, of course!). The developers can see each other’s screens, get their own mouse cursor on it, and use voice chat to talk about and resolve issues in real time. This process is very effective, because it allows for quick feedback loops and improves overall programming efficiency. Depending on team members' personalities, one developer might be more comfortable with pair programming while another prefers solo work. By giving both types of personalities an opportunity to try remote pair programming, you will likely find that your team likes using remote pairing or they don't. You may even find that after getting a taste of pairing remotely, they want it all of the time! If so, make sure you have at least 2 monitors per person working in pairs or set up a second screen available specifically for remote pairing. 

Who Should Use It?

It doesn’t matter if you’re in an office or working from home, remote pair programming has a number of benefits and can be very useful if you have a developer who doesn’t work with anyone nearby. It also helps facilitate communication between colleagues when there are time zones between them. This technique is often used when developing complex software like operating systems or large-scale applications that require constant attention to detail. Remote pair programming allows one engineer to lead while another follows along; it encourages transparency and rapid feedback so mistakes can be caught quickly and fixed easily. Since errors are noticed as they happen, bugs aren’t allowed to hide until released into production at which point they could cause widespread issues for your clients or company.

Things to Look Out For

In a remote environment, it's easier to miss some of those subtle cues that you'd normally get from being in a face-to-face meeting. For example, when someone asks you to repeat yourself or doesn't answer your question directly; these things usually give away a bit more about their thoughts. It is important to be aware of these little clues and adjust your attitude towards communicating with them accordingly. For example, if they ask you to repeat yourself, it might mean that you are talking too fast or not speaking clearly enough; they might not be catching all of what you're saying so try slowing down. If they take a long time answering your question or avoid answering altogether, it may be because they feel like you didn't really understand their point - try asking for clarification on what you don't understand. All these micro adjustments will start to build over time as you work with people remotely and make sure that everyone is feeling more comfortable working together remotely every day. The bottom line: no matter how well you know each other, communication can always be improved - just pay attention!

Tips For Success

If you’re just starting out with remote pair programming, there are a few things you should know. First of all, remote pair programming can be incredibly rewarding; however, it does take some time to get used to. Here are some tips for successful remote pairing: Face-to-face conversations about your screen and code require patience, understanding and mutual respect. It is particularly important to agree on when you both need to talk or if it's okay not to say anything at all. Make sure you can trust your partner by seeing them in action during short pairing sessions before trying longer ones over a distributed network. Remember that working remotely means people need more time, which makes effective communication even more critical than usual. Don't expect miracles from yourself; as Albert Einstein said If we knew what we were doing, it wouldn't be called research. Also mind your posture: sitting for too long causes back pain and neck strain so try getting up regularly. 

Setup of a Pair Programming Room

Pair programming rooms can come in all shapes and sizes, from dimly lit backrooms to bright and airy conference rooms with wall-to-wall windows. However, all pair programming rooms should include several important features to help everyone get the most out of their experience while working together. In this blog post, we’ll look at the five most important features every pair programming room should have in order to maximize productivity and encourage collaboration and creativity in teams of programmers looking to do some great work together.

Blocked Off Room

Sometimes, room layout can get in your way of being productive while you work. This is especially true for programmers who need to concentrate on their work. You’ll want to avoid rooms with excessive distractions, including music and other people working near you. Instead, you should set up shop in a private office or quiet room where nobody will bother you. Blocked off rooms are excellent for pair programming since it keeps your focus on each task at hand. If you end up pairing with someone who tends to chit-chat during development, they won’t be able to distract you while you code. Chances are you’ll find yourself more focused when working out of blocked-off offices.

Natural Light

Working by natural light helps create a better work-life balance. Spending all day inside of an office can make you feel like you’re working constantly—leaving less time for socializing and exercise. Studies show that having access to natural light helps improve focus, mood, and productivity; why would you not want to take advantage of it? Additionally, keep in mind that sitting too close to your monitor could be detrimental to your health; opt for moving your chair farther away from your desk at least once an hour. 

Natural light
Let the sunshine in!

Whiteboard Wall

A whiteboard wall is a must in any pair programming room. Whiteboards are always available when you need them and there’s no need to rearrange your furniture if you don’t have space in your office. As with every piece of equipment in a pair programming space, choose a whiteboard that’s big enough to work on with another programmer—anything smaller than six feet by three feet is just asking for trouble. If possible, get one or more dry-erase electronic writing pads that will let multiple people simultaneously edit their own copy of what someone has already written on a board. 

A Biiiiig whiteboard

Lots of Desks

The best pair programming rooms should be set up with lots of desks, allowing pairs to easily form and disband. This is because pair programming works best when programmers switch off often—and having a large number of desks ensures that people who want to switch partners can do so quickly. Also, by keeping a large number of desks free at all times, you prevent pairs from getting attached to each other and makes it easier for anyone in your office to start working on a project together. A lot of natural conversation also happens between pairs sitting at adjacent tables.

Projector / Large Monitor

A large-screen projector or monitor is a must for any pair programming session. It allows all team members to see what’s happening on each others' screens, facilitating better communication. Any projector will do, but you might want to keep in mind size of your office and distance from your work station. You may also want to consider things like audio output, where you'll be storing your laptop, and whether or not you need additional peripherals. (Projectors typically don't come with built-in microphones.)

projector
However, we DO NOT recommend that kind of projector

We hope you enjoyed our article about the best pair programming room, setup and material. With this knowledge, we know you can make the most of your company's pair programming time and collaborate with ease during your next pair programming session. So what are you waiting for?

Pair Programming Partner Picking Principles

Pair programming is an excellent technique that can help you to develop your skills and help you learn from another person's perspective on software development. However, picking the right partner can be difficult, and this guide will help you pick the right person who will complement your working style and bring out the best in you as a developer. By following these pairing partner picking principles, you’ll have a much more productive experience.

Expert-Expert pairing

You will want to find someone who is either better than you or at least at your level. When you choose an expert as a pairing partner, be prepared to take on more responsibility for writing code. The best way to balance out expertise levels is by partnering with someone who is slightly below your level. They’ll ask great questions that force you to think about things that might not have otherwise occurred to you; but they won’t be able do everything for you.

Expert-Novice pairing

The most common pairing type is expert-novice, where one person is more experienced than another. Expert-novice pairings are most useful when you have high variability in skill level or knowledge among your team. For example, if you have a team of five developers working on different parts of a single product, it can be very useful to have one developer who knows each part well and one developer who is just learning that part. The expert partner can help by explaining concepts and answering questions as they arise. Another example would be having an expert interviewer paired with someone who is practicing their interviewing skills. Having two people who are highly skilled in different areas paired together may result in conflict due to differences in style or work habits.

novice - expert
"Teach me your ways, sensei" - © Sony Pictures Entertainment

Novice-Novice pairing

This means pairing up developers who are both novices at pair programming. This has two advantages: 

The disadvantage of novice-novice pairing is that it limits how quickly both developers can progress their skills. After all, if both members of a pairing team are beginners, then there’s only so much either developer can learn—and even then things move slowly because teaching or explaining complex concepts takes time away from development work. 

Extrovert-Extrovert pairing

If your pair is an extrovert and you are also an extrovert, you will be able to keep each other motivated to stay on task. If one of you becomes distracted, it's likely that at least one of you will notice. You will inspire each other to solve problems and brainstorm innovative solutions. This pairing enables both of you to contribute equally without any awkwardness or pressure. This type of pairing is ideal for people who have not had much experience with pairing before. For example, if you do not know anything about programming yet but want some help with learning how to program, then partner up with someone else who wants some help as well. The two of you will have fun working together since you'll learn how to program together!

Introvert-Introvert pairing

When you have two introverts on a team, there’s no question that pairing can help them work better together. Each person will have their own strengths and weaknesses, so it’s a great idea to try and pair up with someone who complements your own skillset. This pairing style is especially effective for cross-functional teams where each team member has different roles to fulfill. Here are three guidelines to keep in mind when pairing with an introvert :

  1. Always start pairing during prework—and only if needed. Never start working on critical tasks straightaway; save these tasks for later when partner fatigue sets in.
  2. Aim to take turns driving—this way, one of you can stay engaged while the other takes notes or gives feedback.
  3. Switch partners often—the key here is to make sure neither of you get stuck with a teammate you don’t like or work well with. These tips will ensure that both introverts get enough focused time and energy, and everyone else gets time away from screen time!
Thinker
"I am not an introvert, I am a thinker"

Extrovert-Introvert pairing

The idea is that when someone who is an extrovert pairs with someone who is an introvert, they learn to quiet their thoughts and become more reflective. The introverts, in turn, practice speaking up and speaking out. There are two ways you can try extrovert-introvert pairing: At work or at home. If you’re looking for your partner at work, place a posting asking people to volunteer; make sure you ask specifically for volunteers (don’t just say volunteers wanted). Then put each person through a short interview process (in person or over email) to help determine if they’re actually interested. If all goes well, pair them! If it doesn’t go well, end it early.

We hope you enjoyed our article about Pair Programming and the different principles you can use when picking your pair programming partner. With this knowledge, we know that you can make the most of your programming sessions and complete projects with ease. 

Beginners Ground Rules for Remote Pair Programming

You’re about to try remote pair programming for the first time, congratulations!

Set aside fears and biases, here are some pieces of wisdom shared by our daily users, that you can rely on to make sure your first session is a success

Make yourself comfortable

One of the biggest benefits of remote pair programming, is that you get to share knowledge and learn from others, from the comfort of your own desk or home . Make sure you have everything you need, from a nice drink to your favorite backlit keyboard. If you’re pairing from home, remember that a good wifi connection is crucial for a smooth session. 

Another advantage of remote is to use a tool allowing you to work cross OS and IDEs, such as (you guessed it) Drovio

Comfortable
A little bit too comfortable?

Get rid of distractions

Your pairing partner needs you to follow and stay focused, so go ahead and click that “Do not disturb” button, whether that means activating the option on your computer or maybe letting the cat out of the room for a while? 

Turn your video camera on

Be prepared to shine bright and keep your camera on for your first PP sessions. First, it will help you start the session with proper greeting and encourage a more relaxed small-talk.  Moreover, visual clues will help you make sure you’re both on the same page. At some point you might notice your pair looking a bit confused or lost, but too shy to express it and ask you to slow down. 

Camera on
It's a bit too much, no?

Start small

Going from solo to duo programming is a big change, and your first Pair Programming sessions will definitely leave you exhausted. Set aside 30 minutes to an hour maximum for your first session, and keep the same timeframe for the first week(s). Once both roles feel natural to you, you’ll be able to get adventurous and plan 2 or 3 hour long sessions.

Also, make sure you pick up an easy task, one that you’re probably able to figure out on your own. The goal here is to understand the roles and dynamics of this new duo, not to get stuck on an impossible bug. 

Start small
Even Batman started small

Choose your partner carefully 

Senior or junior, experienced pair programmer or not... doesn’t seem to matter that much, as long as you start with someone you are comfortable with. Everyone is afraid of making mistakes and feeling judged. Surprisingly, we noticed that senior engineers tend to ask more questions than junior ones during PP sessions.

As pleasant as it can be to conquer this new territory with your favorite colleague, keep in mind that you’ll soon have to try Pair Programming with another partner, in order to prevent falling into some bad habits. 

Verbally agree on a common goal

This one may seem obvious, but it is necessary for both participants to make sure they understand and share the same objective. This will make more sense once the tasks get harder, as you’ll need to decide and validate the different steps needed to solve a bigger issue, that will help you stay on track later on. 

Common goal
The beginnings of a bromance?

Communicate respectfully

With great power come greater responsibilities.

As the Navigator, you’re naturally taking a more “judgmental” role, so make sure your Driver feels supported and encouraged. Resist the urge to shout “that’s not how it’s done!” and try asking “Why” or “How” questions instead. 

As the Driver, your main duty is to remember to also communicate: describe what you are doing and why. You should never go silent for more than 3 minutes. 

Remember to switch roles

It’s not easy to understand when you should switch roles, so pairing novices often apply the Pomodoro technique: work for 25 min, take a 5 min break, switch roles and work for another 25 min. This is perfect for a first session. 

Once you get more experienced, you’ll be able to determine WHAT will trigger switches instead of WHEN, although timeboxing can totally remain your method of choice. 

Have fun and celebrate small victories!

If you’ve taken time to research pair programming, you’ve probably found different techniques advocating for different rules and requirements. Finding your go-to method and rhythm of choice takes time, so make sure you’re actually enjoying the sessions, rather than feeling guilty for not following rules by the book.  If you feel frustrated at the end of a session, talk about it with your partner and try to understand what bothered you. If you feel proud of the work accomplished, celebrate, this is a big step! 

Enjoy
Enjoy!

Those simple ground rules will help you make sure your team is on the right track and reap benefits sooner than you think. If you’re feeling stuck, our team will be happy to help you, just drop us a message at contact@drovio.com and we’ll come back to you!

The Different Styles of Pair Programming

That moment when two developers are sitting across from each other, each staring into their own screen but working together to solve the same problem. That’s pair programming, and although it can sound strange at first, it’s an approach that has become more common in the world of software development over the last decade or so, with many developers swearing by its benefits. But how do you tell which type of pair programming to use, and when? Let’s take a look at some of the most common types of pair programming and see how they work!

The Driver-Navigator Style

In driver-navigator pairs, one programmer drives for a few minutes at a time while the other navigates. This is often done in coffee shops or open-space offices so programmers don't have to wait for others to arrive at their desks. There are also different styles of driving. For example, you can drive by telling your navigator exactly what code to write next, or you can drive by saying what you'll be doing next - then letting your navigator decide how best to accomplish that goal. The former style ensures that things get done quickly and accurately; but it takes practice to do well.

Pair Programming - Driver Navigator Style

The Unstructured Pair Style

This is probably what most people think of when they hear pair programming. The unstructured style, as its name implies, doesn’t prescribe much other than two people sitting down and writing code. This has many upsides: you can try out new techniques or languages to see how they work (and who better to learn from than your experienced coworker?), and there are no set rules for collaboration, meaning you can work at whatever pace suits you best. Unstructured pair-programming sessions are great for getting a lot done in a short period of time—you have twice as many brains on hand after all—but may not be great if you want someone else looking over your shoulder telling you what to do every step of the way.

Pair Programming - Unstructured Style

The Strong Style Pairing

This type of pairing usually consists in one developer who is designated as driver or navigator for a given time slot. That person will drive most of the interaction with writing code, while his or her pair will provide feedback about design decisions, ask questions about problem solving and check whether all requirements are met. This approach tends to be more efficient when you’re dealing with very specific tasks that require deep knowledge about a given domain or technology. It’s also good for beginners who may need guidance in some areas before being able to fully take charge.

Pair Programming - Strong Style

Ping-Pong Pairing

When pair programming, ping pong pairing means you and your partner trade off roles: One person writes code, while their partner reviews it. The driving and navigator roles will switch back and forth as well; however, because one programmer will know more about what to do than his or her partner, there is usually a bit of lead time to get things set up for that person to drive before they begin typing again. The end result is that both partners benefit from working on one task together without switching back and forth between tasks. It also creates a dynamic where neither partner can dominate or take control over another’s work. Although there are many different types of pairing arrangements, ping pong pairing is a great way to share responsibilities evenly.

Pair Programming - Ping-Pong Style

Backseat Navigator Style

The backseat navigator knows what he wants to do, but doesn’t always know how to get there. In practice, you may find yourself dealing with a backseat navigator in two ways: You both can write code, or you might be pairing with a developer who's looking over your shoulder and telling you what to type. If it's one-on-one pairing and you're a veteran programmer, a backseat navigator can actually help you solve problems.

Pair Programming - Backseat Navigator Style

Tour Guide Style

This style of pairing is used for two developers with different skill sets, such as a junior and senior developer. The lead is responsible for doing most of coding and is usually paired with someone who needs guidance, has specific knowledge that can be used, or just wants to see more. The junior dev focuses on improving their skills by asking questions and learning from what’s happening around them. This pairing is ideal when one person knows more than another about something like a new library or framework. Because both programmers are focused on writing code, there isn’t much time for chit-chat; however if either dev has questions about how something works they can ask before committing code.

Pair Programming - Tour Guide Style

Distributed Pairing

With distributed pairing, pairs are separated in different locations. For example, there may be two people in India and two in Canada; or one person in Los Angeles and another in New York. Pairing is carried out over computer networks rather than face-to-face. Distributed pairing can be used when individuals are located far apart, so no one is forced to travel long distances to meet face-to-face with their partner for pair programming sessions. One major benefit of distributed pairing is that it's convenient for all parties involved. It gives you access to better developers by providing an opportunity to work with specialists who live far away but have specific skill sets that complement your own skillset.

There are many different styles of pair programming. It’s important to understand these differences so you can find what works best for your team. The most important thing is that you choose a method that makes sense for your specific team, then dive in and see