Continual Code Review

A talk on Pair Programming given at Code Camp Wellington 2016.

Transcript

1. Continual Code Review Samson Ootoovak Developer at Flick Electric @ootoovak 1 / 66
2. Pairing @ootoovak 2 / 66
3. Continual Code Review @ootoovak 3 / 66
4. Continual Code Review Continual Rubber Ducking @ootoovak 4 / 66
5. Continual Code Review Continual Rubber Ducking Continual Design Meeting @ootoovak 5 / 66
6. Continual Code Review Continual Rubber Ducking Continual Design Meeting You get the idea... @ootoovak 6 / 66
7. The Hook You may have heard about continuous integration, continuous deployment, all the continuous things. @ootoovak 7 / 66
8. The Hook You may have heard about continuous integration, continuous deployment, all the continuous things. But what about the continuous people stuff? @ootoovak 8 / 66
9. Pairing! What is pairing even? Why am I talking about it? What does pairing have to offer? How do I even? Things to look out for. And some helpful quotes! @ootoovak 9 / 66
10. Please tell me about pairing? In this talk when I say Pairing I mean Pair Programming. @ootoovak 10 / 66
11. Please tell me about pairing? In this talk when I say Pairing I mean Pair Programming. Some people call it Peer Programming but most use Pair (as in two). @ootoovak 11 / 66
12. Please tell me about pairing? In this talk when I say Pairing I mean Pair Programming. Some people call it Peer Programming but most use Pair (as in two). Pairing came out of Agile software development. @ootoovak 12 / 66
13. When you are Pair Programming there are a few key elements. @ootoovak 13 / 66
14. Setup Equipment: One computer Sometimes, one mouse, one keyboard. But sometimes one mouse and keyboard each connected to the same computer. Big or dual monitors helps. @ootoovak 14 / 66
15. Setup There are traditionally two people: One " driver " One " navigator " @ootoovak 15 / 66
16. Driver Is the only person controlling the computer. They are typing in the code. @ootoovak 16 / 66
17. Driver Is the only person controlling the computer. They are typing in the code. Or... looking up docs or error messages online. @ootoovak 17 / 66
18. Driver Is the only person controlling the computer. They are typing in the code. Or... looking up docs or error messages online. Also, their focus is communicating their thoughts with their pair. @ootoovak 18 / 66
19. Navigator The person thinking about what is going on and what is coming up. Not controlling the computer. @ootoovak 19 / 66
20. Navigator The person thinking about what is going on and what is coming up. Not controlling the computer. They are trying to think understand what the driver is doing at all times. @ootoovak 20 / 66
21. Navigator The person thinking about what is going on and what is coming up. Not controlling the computer. They are trying to think understand what the driver is doing at all times. Also, their focus is communicating their thoughts with their pair. @ootoovak 21 / 66
22. @ootoovak 22 / 66
23. Driver: Their focus is communicating their thoughts with their pair. Navigator: Their focus is communicating their thoughts with their pair. @ootoovak 23 / 66
24. Driver: Their focus is communicating their thoughts with their pair. Navigator: Their focus is communicating their thoughts with their pair. @ootoovak 24 / 66
25. “Communicate! If you have never paired before, always check in with your partner at the beginning, during and after.” Olivia Baddeley Developer, Flick Electric - @baddjuice @ootoovak 25 / 66
26. That's pretty much it. There are a bunch of other rules suggestions about how to do it but I think it is largely up to your team, your pair, on what works best for all of you. @ootoovak 26 / 66
27. My experience AKA "Why should I listen to you?" @ootoovak 27 / 66
28. Benefits @ootoovak 28 / 66
29. Organisation PoV Two developers on one computer isn't that a waste? @ootoovak 29 / 66
30. Benefits - Organisation It's Teams++ @ootoovak 30 / 66
31. Benefits - Organisation It's Teams++ @ootoovak 31 / 66
32. “Think of it like rubber ducking, but the rubber duck responds to you, asks questions and points out things that you miss.” Cara Hill Developer, Rabid Technologies - @ilikeprettycode @ootoovak 32 / 66
33. So how do you do it? @ootoovak 33 / 66
34. Types First lets quickly talk about types of pairing before we get into the how. @ootoovak 34 / 66
35. Who are you pairing with? Because pairing involves other people (gasp!) who you are pairing with should be on your mind. @ootoovak 35 / 66
36. “I can't Objective-C for jam, but we had a great session with him explaining Objective-C to me and me explaining patterns and things to him.” Ben Amor CTO, ShowGizmo - @shortmethods @ootoovak 36 / 66
37. Strategies @ootoovak 37 / 66
38. Start slow @ootoovak 38 / 66
39. Check in @ootoovak 39 / 66
40. Setting up expectations @ootoovak 40 / 66
41. “Talk at the beginning and discuss expectations and what each person wants to get out of the experience.” Libby Schumacher-Knight Developer, Flick Electric - @schuknight @ootoovak 41 / 66
42. Take frequent breaks @ootoovak 42 / 66
43. Find non-pairing tasks @ootoovak 43 / 66
44. Close quarters @ootoovak 44 / 66
45. Talk all the time @ootoovak 45 / 66
46. “Embrace the awkward silence. If you wait an extra 30 seconds, you might be surprised and delighted with what your pairing partner comes up with.” Raquel Moss Freelance Developer - @raquelxmoss @ootoovak 46 / 66
47. Practice @ootoovak 47 / 66
48. Difficulties to watch for @ootoovak 48 / 66
49. It is a completely different and often new skill! @ootoovak 49 / 66
50. Learning to be Vulnerable @ootoovak 50 / 66
51. Tiring @ootoovak 51 / 66
52. Development Styles @ootoovak 52 / 66
53. Exploring @ootoovak 53 / 66
54. Business Time Pressures @ootoovak 54 / 66
55. Anti-patterns @ootoovak 55 / 66
56. Pairing does not mean grabbing the keyboard when you have an idea or understand some concept first @ootoovak 56 / 66
57. @ootoovak 57 / 66
58. It also does not mean checking your texts while someone else types @ootoovak 58 / 66
59. Why put yourself through it? @ootoovak 59 / 66
60. Benefits - Personal Learning @ootoovak 60 / 66
61. “Be open-minded to what they say because they could get you out of a hole in a way that you weren't expecting.” Rob Edgecombe Developer, Axos Systems @ootoovak 61 / 66
62. Wrap Up Pairing is not magic Work up to it Remember it's about the people Celebrate your wins @ootoovak 62 / 66
63. “Appreciate each other or a high-five when the code works or when the tests go green” Vinitha Natarajan Developer, Rabid Technologies @ootoovak 63 / 66
64. @ootoovak 64 / 66
65. Special thanks: Olivia Baddeley Cara Hill Ben Amor Libby Schumacher-Knight Raquel Moss Rob Edgecombe Vinitha Natarajan @ootoovak 65 / 66
66. Samson Ootoovak ootoovak.com @ootoovak 66 / 66