Ben Rady and Matt Godbolt
Pair programming means code review all the time.

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

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