Red Squirrel Reflections
Dave Hoover explores the psychology of software development

Dave Hoover
dave.hoover@gmail.com

Categories
All [Atom]
Craftsmanship [Atom]
Dynamic [Atom]
Intersection [Atom]
Learning [Atom]
Links [Atom]
Polyglot [Atom]
Projects [Atom]
XP [Atom]
Old Blog

Obtivian Blogs

Andy Maleh
Colin Harris
Fred Polgardy
Jake Scruggs
Kevin Taylor
Renzo Borgatti
Ryan Platte
Todd Webb
Tyler Jennings

Archives

June 2008 (4)
April 2008 (3)
March 2008 (1)
February 2008 (1)
August 2007 (1)
July 2007 (1)
June 2007 (1)
May 2007 (4)
April 2007 (3)
March 2007 (5)
February 2007 (6)
January 2007 (6)
December 2006 (10)
November 2006 (5)
October 2006 (8)
September 2006 (8)
August 2006 (5)
July 2006 (12)
June 2006 (7)
May 2006 (5)
April 2006 (5)
March 2006 (4)
February 2006 (2)
January 2006 (5)
December 2005 (5)
November 2005 (3)
October 2005 (3)
September 2005 (6)
August 2005 (4)
July 2005 (7)
June 2005 (14)
May 2005 (6)
April 2005 (8)
March 2005 (9)
February 2005 (11)
January 2005 (16)
Old Archives

 

Fri, 29 Jul 2005

Remote Ping-Pong Programming

In response to my StickyMinds article on ping-pong programming, Ivan Vaghi emailed me with a story of a remote ping-pong programming session. He doesn't have a blog so I figured I would post it here (with his permission)...
Yesterday I tried a remote ping pong coding session with a friend.

The social dynamics and the fun are amazing. If you want to try it out get the MoonEdit collaborative editor and setup a coding session. We split the editor space in 2 parts. While one of us was writing tests, the other just by glancing at the tests was writing the code.. the amount of information that passed through, just by coding, not even by talking about it, is amazing. People also somehow develop social protocols so that they don't get in each others' way.

It is an intoxicating experience :-) Who said that when two minds meet, a third mind emerges? That's the feeling that it gives you while you see the code emerge and evolve. It almost feels like you are looking after a living thing, pruning some code here, splitting some code there, rather than doing actual coding. I guess it's due to small seemingly unimportant changes building up into functional code.

It's amazing when, after having done the work, you replay the session using the 'history' feature and you see the living code evolving, growing, getting fatter, splitting and adjusting to a new position.. it feels like the tests are nudging the code to a new shape, to a new position.

[/xp] permanent link


powered by blosxom