Summary: Panelists Avdi Grimm (twitter github blog book) Charles Max Wood (twitter github Teach Me To Code) David Brady (blog twitter github ADDcasts) James Edward Gray (blog twitter github) Josh Susser (twitter github blog) Discussed in this Episode Driver/Navigator vs Driver/Driver One person writes a test, the other makes it pass (Ping-pong pairing) It can be more productive Code review Shortens code review cycle Higher engagement Raises the quality floor Pairing effectiveness Less likely to rabbit hole We learn from each other Better code quality Transmitting information Lowers your bus number Territoriality and knowledge silos Learning new things from people who know how to do them better Challenging peoples' assumptions Ability to roll new teams in Pass on programming practices and culture Lower defect rates Fewer failed launches Maintainability is higher To get started: Have a neutral setting for pairing. Location. Software. etc. Use a text editor you're both comfortable with. Use driver/navigator. Communicate well. Keep your partner apprised of where you're going Pair programming is a learned skill You have to get your ego in check Reduce barriers to collaboration Picks Google Plus Hangouts (Avdi) Wide Teams Podcast (Avdi) Qido (David) Dove Men's Care Products (David) Castle (On Amazon)(James) subtlepatterns.com (James) Lying by Sam Harris (James) RemotePairProgramming.com (Josh) How to do your own object creation methods (Josh) Adventures of Merlin (On Amazon) (Josh) Meeting People in the Community (Chuck)
