Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By Joe Moore Let's do this thing. What is pair programming? Won't software projects take twice as long or cost twice as much with pair programming? Do I pair with the same person every day? Who owns the code? How do performance reviews work? Do we pair on *everything?* What do I do if my pair goes home sick? What do I do if I can't stand my pair? What if my pair smells bad? What if my pair smells GOOD?! I've given presentations at many conferences, Meetups, and companies on topics ranging from Agile team management to Android messaging frameworks. My presentations inevitably grind to a halt once I mention that I pair program: I'm peppered with questions! I'll answer any and all questions about pair programming and remote pair programming, from the profound to the silly. I have no doubt that we will fill the allotted time with sage advice, educational anecdotes, and your own stories about pair programming. Help us caption & translate this video! http://amara.org/v/FG3b/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In a talk titled "I Have Pair Programmed for 27,000 Hours: Ask Me Anything!" at LA RubyConf 2014, Joe Moore explores the concept and practice of pair programming, inviting the audience to ask questions about this software development technique. Pair programming involves two programmers or a programmer and a designer working together on the same computer to solve problems jointly. Moore shares his extensive experience and provides answers to common inquiries surrounding the practice, addressing both its benefits and challenges. **Key Points Discussed:** - **Definition of Pair Programming:** - It involves two people working together on a single computer, often using tools like Skype and screen-sharing for remote collaborations. - **Overcoming Nervousness:** - Moore acknowledges that nervousness can be a constant feeling at the start of a pairing session but emphasizes that rapport helps ease this sensation over time. - **Benefits and Flexibility:** - He argues that pair programming is effective for most tasks, including writing emails and tackling complex programming challenges. - **Communication:** - Effective communication (verbal and nonverbal) is crucial; silence can hinder remote pair programming. - **Disagreements in Pairing:** - When disagreements arise, they can often be resolved through negotiation or by consulting a third party. It's important to maintain a compromise to achieve the best solution. - **Role Switching:** - The roles of 'driver' and 'navigator' in pair programming should switch frequently to maintain balance and energy. Nonverbal signals help in this transition. - **Individual Preferences:** - While some developers prefer working alone at times, pairing enhances accountability and quality. Moore reflects that solo work can sometimes yield poorer results. - **Learning Opportunities:** - Pair programming promotes knowledge sharing and cross-training, benefiting both junior and senior developers. - **Remote Pairing vs. In-person Pairing:** - Remote pairing can sometimes lead to a more focused experience compared to work in a noisy office environment. - **Taking Breaks:** - Moore emphasizes the importance of breaks to prevent burnout, advocating for a balanced approach to pair programming. **Conclusion:** Overall, Joe Moore's session sheds light on the value of pair programming, highlighting its collaborative nature, potential for deep learning, and practical considerations for effective implementation. As attendees engage with these insights, they leave with an appreciation of how this technique can enhance their development processes and teamwork dynamics.
Suggest modifications
Cancel
