Showing Revision 1 created 02/23/2015 by Code.org.

1. Title:
   Pair Programming
2. Description:

   Featuring Fiona and Semira from Generation Code.
   Special thanks to Eckstein Middle School for use of the space.

3. 5069 0:05 - 0:11
   Today we're going to learn about pair programming.
   In pair programming, you work as a team. Why
4. 11250 0:11 - 0:17
   should two people use one computer? Because
   two heads are better than one. We work together
5. 17400 0:17 - 0:24
   in an interesting kind of way. Because we're
   interesting people. We are interesting people.
6. 24340 0:24 - 0:28
   In pair programming, you and your
   partner are going to sit down together at
7. 28460 0:28 - 0:33
   one computer and you're both going to work
   on the same project. Right now we're working
8. 33330 0:33 - 0:36
   on Code Monsters!
9. 38320 0:38 - 0:43
   In pair programming, one
   person is the driver and the other person
10. 42809 0:43 - 0:47
    is the navigator, just like driving a car.
11. 47320 0:47 - 0:51
    Your choice, driver or navigator? Driver.
12. 51040 0:51 - 0:57
    The driver sits at the computer and is the one using
    they keyboard, mouse, or touch screen and
13. 56579 0:57 - 1:02
    controls the main actions of the computer.
    I'm setting the arrows so that they make the
14. 61789 1:02 - 1:07
    character move in the direction that he's
    trying to move. And the other person is the
15. 67340 1:07 - 1:12
    navigator. The navigator helps the driver
    by answering the driver's questions and pointing
16. 71700 1:12 - 1:15
    out potential problems or mistakes.
17. 74760 1:15 - 1:19
    Go left. Instead of righty tighty, go right.
18. 80160 1:20 - 1:25
    Communication
    is key to successful pair programming. Don't
19. 84980 1:25 - 1:33
    DON'T: insult your partner. DO: be respectful. DON'T
    be a bossy navigator, because nobody likes a backseat driver.
20. 93020 1:33 - 1:39
    Why can't you do this? Wait, hey! Stop that, give it back. (DON'T grab the driver's mouse/keyboard)
21. 99800 1:40 - 1:45
    Communication is key to successful
    pair programming. You and your partner
22. 104980 1:45 - 1:49
    should always be talking.
    (DO talk to one another about the work)
23. 108980 1:49 - 1:54
    The driver can explain what s/he is doing.
    (DO explain what you are doing)
24. 114120 1:54 - 2:01
    The navigator can help suggest what to do next.
    (DO think ahead and make suggestions)
25. 120820 2:01 - 2:06
    The navigator should be thinking about
    the big picture and the driver focuses on
26. 125659 2:06 - 2:09
    the details. Both roles are important
27. 129019 2:09 - 2:12
    Want to switch? Okay. I'm the driver now. (DO switch roles often)
28. 132179 2:12 - 2:15
    Be sure to switch roles often.
29. 135200 2:15 - 2:18
    Wait a second, why isn't this working?
30. 137720 2:18 - 2:22
    You need to attach it up there,
    look there's a hole.
31. 142000 2:22 - 2:26
    Did you see how my partner helped me to figure out the puzzle with fewer tries?
32. 146140 2:26 - 2:29
    She caught my mistakes. Pair programming
33. 149269 2:29 - 2:32
    is all about working together as a team.
34. 157280 2:37 - 2:40
    DO: Be respectful, talk to one another about the work, explain what you are doing
35. 160180 2:40 - 2:43
    DO: think ahead, make suggestions, switch roles often.
36. 163100 2:43 - 2:46
    DON'T: be a bossy navigator or grab the driver's
    mouse/keyboard.