CSE 326

Autumn 2005

Pair Programming Teams

1. Clayton Chang, Amihan Beltejar
2. Austin Cargol, Daniel Davenport
3. Gloria Demartelaere, Anthony Gibbon
4. Jordan Eisele, Chistopher Gonterman
5. Aaron Gremmert, Brian Harris
6. Cyrus Hui, Yoshito Kosai
7. Kobi Reiter, Chi-Wai Lau
8. Brittany Luk, Patricia Lee
9. Justin Lundberg, Ryan Libby
10. Peter Novotney, Seoung Lim
11. Hsu Ooi, Anna Ma
12. Jordan Rudd, Katie Neuser
13. Brian Steadman, Vincent Pai
14. Quang Tran, William Pittman
15. Yungchang Zhang, Jodi Shi
16. Alex Zheng, Lon Smith
17. Kerry Westphal, Yanni Wu
18. Ziheng Xu, Jian Wu
19. Zhitao Chen, Nathaniel Chapmam
20. Firat Kiyak, Jonathan McKay
21. Jarred Ward, Michael Skinner

What is Pair Programming?

“Two programmers working side-by-side, collaborating on the same design, algorithm, code or test. One programmer, the driver, has control of the keyboard/mouse and actively implements the program. The other programmer, the observer, continuously observes the work of the driver to identify tactical (syntactic, spelling, etc.) defects and also thinks strategically about the direction of the work. On demand, the two programmers can brainstorm any challenging problem. Because the two programmers periodically switch roles, they work together as equals to develop software. “
-- Laurie Williams
North Carolina State University Computer Science

For the first project, the more novice C programmer should be the driver, while the more experienced C programmer should be the observer, at least at the beginning. Once the novice has built up confidence, the roles can start switching periodically. In the few cases that both students are novices, switching periodically can start at the beginning.