c

Requires vulnerability

Power dynamics

https://martinfowler.com/articles/on-pair-programming.html

Code review on-the-go

Keyboard hogging

Intense collaboration can be hard

🐟🐠 (Questions/comments)

Wondering why all the agile/XP stuff (like pairing, TDD, etc) doesn’t seem to work for a heterogenous team? It’s because they were developed by a bunch of white dudes. The practices assume the practitioners all have A LOT of built-in privilege.

No time for self

Different skill levels

Interruptions

Exhausting

Challenges

People of color < white folks

career changers/self-taught < CS degree

women < men

junior < senior

Impatience. Apply the 5 seconds rule.

Micro-management mode

Checking email, using your phone. Make it transparent if you need to.

Drifting apart

Pair rotations

Fast onboarding of new team members

Collective Code Ownership

🚫 Things to avoid

Two modes of thinking combined

Excalidraw

Benefits

Webex

Reflection

Keeping focus

VSCode Live Share

Knowledge Sharing

Setup

Resources

Start

Pair Development

Set a goal and time box

Plan the session

Strong-Style Pairing

πŸ… Pomodoro Technique

Ping Pong

Driver and Navigator

Time management

Styles

History/background

How to pair

More than just two people sitting at a computer

Benefits are medium–long-term

Who has done this before?

Level set