1. Pair Programming

2. Who am I? @_pedro_torres Pedro Gustavo Torres 3. A little bit of background 4. What is Pair Programming? code is produced by two people programming: on one task on one workstation Two keyboards (optional) Two mice (optional) Two monitors mirroring (ideally) 5. Driver 6. navigator 7. Change roles multiple times a day 8. Change roles multiple times a day 9. Change roles multiple times a day 10. Quiz time! In which scenarios are the developers properly pairing? A B C D 11. Setup #1 12. Setup #2 13. Setup #3 14. Setup #4 15. Tackling multicultural barriers 16. All the times in front of 17. except in 18. and in! 19. Collective code ownership 20. bus factor 21. beginners mind 22. Pair rotation lader 23. What about code reviews? 24. The Rock Star 25. newbie 26. junior 27. senior 28. soul mates 29. CVDD 30. badass 31. Engagement / Commitment 32. valuable Stand ups 33. better integration of new team members 34. Less bugs 35. more fun 36. less distractions 37. less interruptions 38. less slacking 39. and comfort zone wise 40. bigger comfort zone! 41. Two heads think better than one 42. Common habits 43. no music / social stuff 44. So is Pair Programming for everyone? 45. It should not be imposed 46. Remotely works? 47. Are estimations affected? 48. What about size or length of tasks? 49. Is it xpn$ive? 50. Is it only for mature teams? 51. Does it scale? 52. Companies that use it 53. Jobs? 54. Careers 2.0 by stackoverflow 428 Pair Programming jobs 422 JavaScript jobs 363 Java jobs 243 Python jobs 199 ASP .Net MVC 197 Ruby jobs 186 PHP jobs 175 Node.js jobs 132 Android jobs 120 iOS jobs on 16th of January 2014 55. Scholars and hands-on fans 56. Common pitfalls 57. Maybe slow 58. or Leeeeeeeeeeeeeroy! 59. Wrapping up 60. Thank you Next time Ill pair present! :P