Ben Rady and Matt Godbolt
The intent of pair-programming is not sitting back and watching the other person programming for 6h.

Episode Summary

Matt and Ben compare different methods of collaboration, and how they work for different personalities. Ben is not a psychologist, but plays one on this podcast. Matt gets very close to explaining what makes for a good pull request, and then doesn't.
... Show More

  • Ping-pong is taking in turns in pair-programming: (writing code, then writing test), switch roles.
  • Choosing a commit message and self-reviewing at the same time.
  • Notice when the pair has been left behind in understanding. To recognize that is a skill.
  • To squash or not to squash before pull-request? Reverting is easier with squashed PRs.
  • The added benefits of pair-programming: learning various problem-solving skills.
  • With well-spaced breaks in-between, Ben can do 6 hours of pair programming sustainably for years.
  • Individual differences in exploring problems. Better talking through or focusing alone?
  • The intent of pair-programming is not sitting back and watching the other person programming for 6h.
  • Pair programming means code review all the time.