Four ways to do pair programming

4 במאי 2010

תגיות: , ,
5 תגובות

My blog has moved. You can view this post at the following address: http://blog.drorhelper.com/2010/05/four-ways-to-do-pair-programming.html

הוסף תגובה
facebook linkedin twitter email

כתיבת תגובה

האימייל לא יוצג באתר. שדות החובה מסומנים *

5 תגובות

  1. Swapneel5 במאי 2010 ב 20:34

    "Tester – Coder" – should be industry standard.

    הגב
  2. Jesus Salas5 במאי 2010 ב 21:06

    If your environment is Visual Studio.

    Why not try wave-vs.net Pair Programming Addin?

    You can code together with other developer in real time each one seating on his own computer.

    Is better than to be force to be a 'passenger'

    don't think so?

    🙂

    הגב
  3. chris6 במאי 2010 ב 0:12

    we call tester-coder 'ping ponging' one dev writes a test, then the other dev makes it pass before writing a failing test and passing back to first dev to make it pass

    הגב
  4. Travis Calder6 במאי 2010 ב 5:17

    As an extension of "Tester-Coder", my favorite style is "Ping-Pong". I write a failing test, then you make it pass and answer back with your own new failing test, which I make pass. Repeat until all test-cases are exhausted.

    When running "Turn-Based", what goal should your passenger have?

    I've found the most effective, for teams I've been on, is a "navigation"-centric approach, where the passenger maintains a big-picture overview of what's left to do, and discusses the remaining goals with the driver often enough to keep him focused. Has anyone else done similar?

    הגב
  5. Mr Matt6 במאי 2010 ב 7:45

    I have done pair programming for about five years now. Here is how we do it. We do the one mind four hands approach. We use terminal services and one session remotes into the other so both parties have complete control of the mouse and keyboard. We both work remote so we talk on headsets all day too. Each person takes a turn at being the lead. When one person tires the other takes over. We can keep momentum going all day this way. You end up refactoring/code reviewing in real time because you are constantly talking about what you are writing and the person not currently driving is overseeing the work, looking things up, and offering ideas and support. We have very few defects and great code quality operating this way.

    You really have to have a compatible partner to make this work. Getting used to each others style and thought processes takes some time. Once you are in synch, your productivity will soar. It's even better if you have different strengths as you can learn from each other in the process. If my partner goes on vacation I feel like half my brain is missing. I wouldn't trade pair programming for anything.

    הגב