[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Pair Programming with Subversion

From: <andy.glew_at_amd.com>
Date: 2004-04-13 04:00:30 CEST

> That's really not the usual way pairing works -- I'm
> suprised you're seeing any benefit to both of you working completely
> separately. Pairing is really all about two people at one computer,
> constantly able to discuss what they're doing and where they're going.
> Pairing this way means that it doesn't matter who checks in the code -- both
> of you will know about it and so either author is acceptable.


(0) I started this "dual monitor pairing" because the
first guy I roped into pairing with me refused,
point-blank, to try single monitor pairing. It works
pretty well, well enough that I refuse to go back
to non-pairing.

Maybe I should try single monitor pairing again.

However, I do not think that Subversion should
foist a particular development methodology / pairing
style on me.

(0.1) As I said earlier, my friends who are doing single
monitor pairing also report annoyance with Subversion's
permissions handling.

(1) If you follow the XP mailing lists and wikis,
you will see all sorts of pairing styles described,
ranging from

   * the ideal, single monitor, 2 people,
     pairing, with exactly equivalent working

   * single monitor "tripling"

   * single monitor, 2 people, different
     environments - requiring people to switch

   * my style: dual monitor, same room, 2 people

   * geographically separated pairing:
     2 monitors, shared VNC sessions,
     IRC and voice line, sometimes video

In all except the first, Subversion's permissions
handling is annoying.

(2) Do you pair?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 13 04:01:34 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.