Why & How We Remote Pair Program

The video of this talk is available on the ATLRUG YouTube Playlist at http://bit.ly/1gCjO4f. The excellent Q&A session starts at 31 minutes.

Brandon Dees and I gave a this talk about how and why we do remote pair programming when he lives in Nashville, TN, and I live in Johns Creek, GA (a 416 mile round trip) on Wednesday, October 9, 2013 at the Atlanta Ruby Users' Group (ATLRUG).

We cover the pros and cons of remote pair programming. Explain a bit about how our typical work day is structured. Finally, we go into what gear is required and show off the studio gear that we have put together for our own use.

If you take away only one thing, please remember that good programming is ultimately about teamwork. It requires continual communication and mutual respect.

Oh, by the way, we did indeed remote pair program this presentation using Google Slides.

Transcript

1. Why & How We Remote Pair Program by Brandon Dees and Frank Rietta
2. “Iron sharpens iron, and one man sharpens another.” Proverbs 27:17 (ESV)
3. Good programming is ultimately about teamwork. It requires continual communication and mutual respect.
4. Pros of Pair Programming • Accountability, Intensity, Focus • Knowledge Transfer, Shared Learning • Combined Knowledge, Problem- solving • Rapport > Competition • Solving problems > Egos • Continual Code Review
5. Cons: Why Not Work Remote / RPP • Scheduling Difficulties • Technical Obstacles ◦ Software Compatibility ◦ Connectivity ◦ CPU / Memory intense • Not the same as sharing an office ◦ Hallway conversations, group interaction limited ◦ Including clients amplifies the other issues
6. The Prescribed Pairing Methodology • Two Programmers, One Computer • Comfortable Chairs • 1 (or 2) keyboards and mice • Switching Roles ◦ Navigator ◦ Driver • Good Etiquette ◦ “Do you mind if I drive for a bit?” • Focus Photo Credit: Lisamarie Babik / Wikipedia
7. Use what works • Pairing is about optimizing communication within the development team • Programming is all about communication in the first place ◦ Translating what client says to real requirements ◦ Between requirements and machine behavior ◦ Between past, present, future developers/selves • Your workflow should, above all else, optimize for effective communication
8. Our Daily Routine • Schedule a kickoff time ◦ Formal standup can be simulated remotely, YMMV • Get the distractions out of the way first ◦ Coffee refills ◦ Stretching ◦ Hacker News / RSS Feeds ◦ Urgent client communications / business needs • Review priorities (in Tracker or general) • Work together on a project OR divide tasks individually in a virtual shared office
9. Our Remote Workflow Three major components: • Telepresence • Collaborative editing • File Sharing
10. Telepresence Tools • FaceTime (least resource hog) ◦ plenty of video/audio options • G+ Hangout ◦ Up to 10 video feeds ◦ Cross-platform ◦ Client-friendly ◦ Includes Screen-sharing • XMPP chat client fallback
11. Collaboration Tools • Google Drive Collaboration • Screen Hero: RDP/VNC on steroids • SSH + tmux/screen ◦ Byobu: jumpstart configuration
12. File Sharing Tools • We ♥ BTSync ◦ DIY Dropbox, P2P, secure/private • Dropbox as the LCD ◦ Plenty of Dropbox competitors; most have technical advantages ◦ … but everybody has Dropbox
13. The Gear Minimal cost of entry (no excuses) • Solid, fast internet connection (up + down) ◦ Failing this, SSH + telephone is useful fallback • Own a decent computer • Macbook is already sufficient • USB Headset ($xx) • USB Webcam ($xx, optional)
14. Beyond the Basics The internal microphone in the MacBook Pro and MacBook Air are good, but pick up a lot of fan noise and also room echo. A USB headset will have better sound quality. A podcaster`s microphone (condenser) will sound even better.
16. Blue Snowball USB Mic Frank’s $300 Gear
17. The Blue Snowball Microphone with a Pop Filter
18. Philips 425264 11-Watt (60-Watt) A19 LED Household Daylight Light Bulbs, Dimmable Lighting is very important to get good video that is not dark and grainy.
19. Brandon’s Gear • sorry I forgot to take photos
20. Blue Yeti USB Mic, ~$100 • Highly versatile multi-mode mic • Great sound quality • 3.5mm monitor and DAC • Needs vibration isolation
21. Neewer Scissor Arm Stand, ~$25 • Inexpensive • Does the job • Includes XLR • Includes Shockmount
22. IMAGE Pop Filter ~$15-25 • Double screen • Good clamp design • No need to spend more • Not necessary for video chat but important for closer-range recording
23. Rosewill RHTS Headset, ~$50 • Excellent sound • External processing • Detachable mic boom • Surround sound + simulated sub for gaming/movies • Rough edges, but very good all-round value
24. Barebones gear example • iMicro IM320 USB Headset, ~$11 • 7.1 Channel USB External Sound Card Audio Adapter, ~$7 w/ shipping • Cheapo USB “security cam,” <$10 at under $50 worth of baseline gear, you have no excuse not to start.
25. Resources • www.pairprogramwith.me • www.remotepairprogramming.com • www.screenhero.com • www.wideteams.com
26. let’s have a discussion Questions?
28. Bonus Slides That were not used in the live presentation
29. 12 Practices of Extreme Programming (1999) According to Kent Beck: ★ Planning game ★ Small releases ★ Simple design ★ Testing ★ Continuous integration ★ Refactoring ★ Pair programming ★ Collective ownership ★ 40-hour week ★ On-site customer ★ Metaphor ★ Coding standard
30. Sennheiser PC 151 Binaural Headset with Noise-Canceling Microphone & Volume Control $65 ($47 now)
31. Logitech Wireless Gaming Headset G930 with 7.1 Surround Sound $160 ($105 now)
32. Sony MDR-RF970RK Wireless Stereo Headphones They work for me, but there are better options.