Patrick Wilson-Welsh's Page

I've been asked on-line and off-line for this recently, so here it is.

Corey Haines and J.B. Rainsberger and I are mostly converging on the following recipe for running something you want to call a CodeRetreat. This recipe may evolve, but our collective desire is that if you diverge very much from this recipe, however useful that divergence may be, you do not call your diverge… Continue

Hi All:

At CodeRetreat MI-7-11-09, we did some "whole application, customer-perspective" ATDD, using JBehave, that we have not done at past CodeRetreats. I hope the lessons learned will infect and assist future CodeRetreats. Rob Park has summarized it all beautifully here:

http://agileintention.blogspot.com/2009/07/top-down.html

Cheers, and thanks, Rob!

--Patrick

Hi All:

Cheezy (Jeff Morgan) has graciously aggregated some of the code from the CodeRetreat at Gale/Cengage in Farmington, MI on 07-11-09, and has put it on his github. You can find it here:

http://github.com/cheezy/coderetreat3/tree/master

Thanks, Cheezy!

--Patrick

Hey Guys. We will likely top off the attendance at CodeRetreat #2 at around 40 people; otherwise it gets too unwieldy. Since it is still more than a month away and we already have 6 folks signed up, please sign up soon if you are serious about attending. We haven't begun yet to pound the Pillar ranks of coders looking for attendees, nor the very large network of coders known to LeanDog in Cleveland. That's when the floodgates will op… Continue

I read a recent post on a local technical user's group thread. It was all about how this guy hates pair programming, which I personally am addicted to, and which I believe is an essential practice and skill for agile teams.

At work, you may not pair, you may not want to pair, or you may want to pair all the time. No matter. Fair warning: at CodeRetreat, we will pair on everything.

No code will be written without at least two people looking at it while it is being written. The rationale is stra… Continue