[wilmoore]

> I don't understand why you'd do pair programming with two new hires!

There's nothing wrong with two new hires pairing. A few things a pair could be doing while the other is writing code:

1. Spike out a refactor of the current viewable block of code that the other pair just wrote or is currently writing. Looking at it as a spike instead of a hard refactor allows a pair partner to experiment and if the spike doesn't result in something better, throw it away; no harm done.

2. Jump ahead and spike out a function that the pair might need soon, but isn't ready to consume yet.

3. Watch for pair getting stuck and help them think. Ask questions like ... are you stuck or just taking a mental break? That's a helpful question because it makes them more comfortable taking mental breaks when they need one without fear that you're judging them.

Keep in mind, pairing is AMAZING when deployed with empathy and less judgement. For those that feel like they are being judged when pairing is likely because you are a bit judgmental when the shoe is on the other foot.

FYI, teams that pair daily, get more done and team members feel less lonely and more like a real team. Go Warriors.