Pair programming: when it helps

How it works

Two people work on one task at one screen. One types; the other follows, asks questions, spots mistakes and thinks a step ahead.

The roles swap regularly — usually every twenty or thirty minutes, so both stay engaged rather than one typing while the other is bored.

Remotely: a shared screen and a voice call. It works much the same but demands discipline, since it's easier to drift.

Why two people are sometimes faster

It sounds paradoxical: two people doing one person's work. But in certain cases it wins:

Mistakes are caught immediately. What review would find in two days is found in two minutes.

Fewer dead ends. When one gets stuck, the other offers a different angle. Alone, the same spot can consume half a day.

Less distraction. In a pair it's awkward to go and read the news. Concentration is noticeably higher.

Knowledge spreads. Both understand how that piece works. Afterwards either can fix it.

When it's justified

Teaching a beginner. The strongest case. Two hours in a pair teaches more than a week of solitary digging: they see how an experienced person thinks, what questions they ask, how they track down a cause.

A hard or unfamiliar task. Where the solution isn't obvious, two heads genuinely help.

An important piece. Where a mistake is expensive: money, permissions, data migrations.

Knowledge transfer. When the only person who knows a system is going on leave.

When it only gets in the way

Routine work. Mechanical tasks that need no thought. The second person will be bored.

Mismatched pace. If one is far faster, the other stops participating and becomes an audience. That requires deliberately slowing down and explaining.

All day. Pairing is more tiring than working alone: constant concentration and conversation. More than two or three hours at a stretch is rarely productive.

When one wants it and the other doesn't. An imposed pair works badly.

Doing it properly

Think aloud. Both of you. A silent pair is one person working and one watching.

Swap roles. On a timer, so you don't forget.

Whoever types doesn't decide alone. Otherwise the other becomes a spectator.

Don't grab the keyboard. Say it in words. Taking over someone's keyboard is a reliable way to spoil the process.

Take breaks. At least five minutes every hour.

Especially useful for beginners

If you have the chance to pair with someone more experienced, take it without hesitation. It's the fastest form of learning available: you receive not a finished answer but a way of thinking.

The reverse holds too: explaining your decisions in a pair is the best preparation for an interview, where you'll have to reason aloud.

On a team project you can arrange it yourselves: once a week, sit down together on one task. Even if you're both beginners the effect is noticeable — together you get through places where either of you alone would be stuck for days.