Pair programming involves two programmers working together, with one typing and the other reviewing the work. It allows for knowledge sharing and immediate feedback. When used selectively, it can produce higher quality code and help onboard new programmers. Mob programming takes this further by having the entire team work together on one task using one screen and keyboard, rotating who physically types. It aims to improve shared understanding and code quality through extensive collaboration, but may reduce delivery speed and be challenging for those who prefer individual work. Effective use of these techniques requires open communication, shared goals, and avoiding forced participation.

1. Pairing and Mobbing
A Conversation

2. What is Pair Programming?
Hint: It's not a sledge hammer.

3. Pair
Programmin
g as a Tool
Two programmers
working together – one
typing, one talking
Knowledge share
Learning a codebase
Code style
Conventions
Patterns
Immediate feedback
loop
May produce less
defects
Works well with TDD
Use as necessary – not
all the time

4. Pair Programming Pairs
Novice – Expert
Knowledge share
Good for onboarding
into a codebase
Encourage the novice
to ask questions
Expert – Expert
Can be costly, so used
sparingly
Encourages bouncing of
ideas

5. Pair Programming Pitfalls
2 people working on 1 thing
rather than 2 people working on
2 things.
Some devs hoard knowledge
and aren't about sharing.
Some devs aren't interested in
learning.
When forced, a lot more grind
and struggles

6. A Positive Tale of Pairing

7. Takeaways of Pairing
Carve time out for it
Understand that the time may not necessarily be
needed
Keep an open line of communication
Work together for the common goal

8. What is Mob Programming?

9. Tenets of Mob Programming
Use one keyboard
and screen
Use a private room
Select a time keeper
to rotate who is on
the keyboard every
15 or 30 minutes.
Everyone gets time at
the keyboard, even
non-programmers.
Take a story from
start to finish, or in
other words: from
planning to coding, to
testing, to done.
Take breaks when you
want.
A session should span
an entire workday.

10. Benefits of Mob Programming
Shared
understanding
and
ownership of
the code base
Everyone all
on one page
Better quality
of code
Massive
knowledge
share
Team bonding

11. Pitfalls of Mob Programming
Whole team on 1 work in process, 1 keyboard – may
be slower delivery times, depending on team bond
and working together
Constant collaboration is troubling for some
Close encounters – illness spread
Needs a lot more buy in

12. The Tale of Quinting

13. Effective Pairing and Mobbing Tips
Take turns driving so that everyone can learn. Know that some folks may feel uncomfortable
about driving – don't force them. Added
pressure can cause internal struggles.

14. Tools for Pairing and Mobbing
Teams / Zoom / Google Hangouts / video conferencing tool
Visual Studio Live Share
Teletype for Atom
Remote Collab for SublimeText
CodeSandbox
Mobster – to track who’s driving, when’s break, and other
timers