Pair programming patterns:
Driver/Navigator — one types, one reviews live. Single committer.
Ping-pong — alternate every commit (one writes test, the other makes it pass).
Mob — N+ developers on the same problem; commits rotate.
Tactics for Git:
- Commit early, push often — pair sessions move fast; lost work hurts more.
- Co-author each commit so credit is automatic.
- Use a shared branch:
feature/x-pairing. Both git pull --rebase regularly.
- Don't force-push while pairing — collaborator might be mid-commit.
- Pre-arranged break protocol: stash WIP, push to shared branch, swap.
Tools that help: VSCode Live Share, Tuple, Pop. They don't replace Git — you still commit normally, but they let both people see the screen + drive the cursor.