1 / 13

Pair Programming

Sept 11, 2019. Pair Programming. Agenda. Preliminaries (8:30-8:40) Pair Programming Discussion (8:30-9:15) Continue Procedures Lab (9:15-9:45) Wrap-up (9:45-9:50). Preliminaries. ACM announcement Peer Support Events Thursday Extra Sept 12 th : 4pm: Snacks in the Commons!

mitchp
Télécharger la présentation

Pair Programming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sept 11, 2019 Pair Programming

  2. Agenda • Preliminaries (8:30-8:40) • Pair Programming Discussion (8:30-9:15) • Continue Procedures Lab (9:15-9:45) • Wrap-up (9:45-9:50)

  3. Preliminaries • ACM announcement • Peer Support Events • Thursday Extra Sept 12th: • 4pm: Snacks in the Commons! • 4:15pm: Science 3821 • “A Just Society Needs Decentralized Tech: Building Online Voting Software at Vocdoni”

  4. Pair Programming Discussion (8:30-9:15) • What are the names of the roles in a pair programming team? • What does each person do?

  5. Pair Programming Discussion (8:30-9:15) • Driver: Keyboard, writing the code, code in front of them • Navigator: higher level thinking how the program should work, thinking ahead, checking for errors

  6. Pair Programming Discussion (8:30-9:15) • Why do you think we ask you to work in pairs? • So both learn what is going on, spot typos quicker, learn syntax, driver gets used to typing • Different perspective, break out of specific thinking • Get unstuck faster, learn from each other • Get a better understanding of where you are compared to others • Expert programming theory, learn from explaining • Harder to pick up bad habits, someone is watching and keeping you honest • Keeps you responsible, have to meet and work on the project • Reminder that you will need to work with people no matter what you do • Can't rely on your partner doing all the work

  7. Pair Programming Discussion (8:30-9:15) • You each have a card with a quote from a previous CSC 151 student • We’ll go around and you’ll each read your card out loud

  8. Pair Programming Discussion (8:30-9:15) • Based on those quotes and/or your own experience so far: • What works well when pair programming? • What doesn’t work well when pair programming?

  9. Works Well: • Listen to one another, don't try to overwhelm the other with own opinion • Pay attention to when coding to spot errors, but don't criticize • Open-minded, don't just shut down ideas • Communication for organizing a meeting and while together, suggest something even if you aren't sure • Be honest, what time you're free and where you are, when you don't understand • Properly explaining things you are having trouble with • Saying and idea even if you just have part of an idea • Should be a meritocracy • Questions are most important • Articulate your ideas clearly, if your partner doesn't understand, you aren't being clear! • Better to code when you are having fun

  10. Doesn't work: • Scheduling: make sure you make time to meet with your partner, it's not only your time • Don't assert dominance even if you're more experienced • Important to switch up, make sure you can do the tasks independently too • Willing to work in the pair, not • Romantic entanglements • Discrimination • Not getting along with your partner, going to happen in the workforce! • Driver Passenger (should be a navigator)

  11. Lab Time • Continue the Procedures lab • Lab Partner is partner for Assignment 3

  12. Lab Time • Write up: • Exercise 8b and any procedures you wrote earlier that you use in 8b • To: csc151-01-grader@grinnell.edu • CC: your lab partner • Subject: [CSC 151-01] Procedures Exercise 8 • First line should be you and your partner’s names • Paste your procedures into the body of the email

  13. Wrap-up • Upcoming Work: • Assignment 3 is up • Partner is your current lab partner • Read about documenting Scheme code for Friday • Submit your lab writeup by 10:30pm on Friday

More Related