John Sladek on 14 Apr 2006 22:45:30 -0000


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Re: [agilephilly] Fwd: [XP] Coding Dojo


It this specific to any programming language?


----- Original Message ----- From: "Jason Nocks" <nocksj@sourcextreme.com>
To: <agilephilly@yahoogroups.com>; "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
Sent: Friday, April 14, 2006 4:59 PM
Subject: [PLUG] Re: [agilephilly] Fwd: [XP] Coding Dojo



The Agile Philly group has been discussing getting a Coding Dojo started, or perhaps just a refactoring fest. Also, we've been discussing using an Open Source project. I thought I'd cross-post to PLUG in case anyone is interested.

Places to host such an activity would be great. Is this something that the
folks at Unisys might be interested in?

Cheers,
Jason Nocks

On Tuesday 04 April 2006 10:20 pm, D. André Dhondt wrote:
This sounds like an interesting way to discuss agile programming in a
future meeting!

---------- Forwarded message ----------
From: Laurent Bossavit <laurent@bossavit.com>
Date: Apr 4, 2006 3:49 PM
Subject: Re: [XP] Coding Dojo
To: extremeprogramming@yahoogroups.com

Greg,

> First, I obviously modeled this off Laurent's activity.  However, not
> having actually participated, I'm doing my best to wing it..

Hey ! That's the way *we* started out. ;)

> I figured that would be a good group size so that everyone could
> follow along (even if they were working as autonomous pairs).

In the Paris Dojo we have only one coding pair, working on a PC
connected to a beamer so the rest of the room can follow along. (We
tried having several pairs, the first session, and found it wasn't
working.)

The basic routine is "Kata": one of the group has done their homework
on a given coding challenge, and their task in the Dojo is to
demonstrate, starting from scratch, their way of solving the
challenge.

The two ground rules is that they have to stick to TDD baby steps,
and each step must make clear sense to everyone in the room. The
audience is supposed to interrupt *only* if they don't understand
what's going on. (Debates on personal preferences, as in "Why are you
leaving the opening brace at the end of the line", are strongly
discouraged.)

This routine scales up to large groups.

The other routine is "Randori", where the coding pair has a small (5
or 7 minute) timebox to complete one or two tests, then the driver
rotates back to the audience, the copilot becomes driver, and one of
the audience steps up to be copilot.

Randori is obviously best suited to smaller groups.

Cheers,

-[Laurent]-
The only meaning of life worth caring about is one that can
withstand our best efforts to examine it. -- Daniel C. Dennett
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug


___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug