Skip to main content

Growing Your Craft: CodeRetreat


If you've never heard of CodeRetreat, you're not alone. I first learned of it a few months ago when Patrick Welsh organized one at our workplace.


CodeRetreat is the brainchild of Patrick and Corey Haines. Patrick is an Agile Developer/Coach, follower of strange dietary practices, and all-around great guy. Corey is the hippie* guru of software development in the Midwest, and a top-tier developer.

* I have no idea what Corey's political and religious beliefs are, if any. He just has long hair.


The event was hosted at LeanDog in Cleveland, in their office on a boat. I can't think of a cooler venue or a better bunch of people to learn with and from.




After meeting the team (and the dogs, who are anything but lean) we went out for drinks and discussion. Our host was Jeff "Cheezy" Morgan, who runs the company with a couple of partners who weren't present for the event, but are probably pretty cool as well. Everyone had something interesting to say, especially Paul Nelson (a Windows-hating Mac fanboy, but otherwise excellent pairing and drinking partner).


We used Conway's Game of Life as the focus out our programming work, but made very little progress on solving the game as a problem. Instead, the focus was on learning new (and better) ways to create an emergent design through Test Driven Development. Patrick did a great job of talking us all down from the wall when it came time to delete our code and start over again - something we did every 45 minutes or so.


I had several great conversations while pairing with different people. Some of the things that stuck with me the most came from Corey. Here is a summary of what I wrote down at the time:


The wisdom of Corey:

  • You don't change code under red - you add (& duplicate if necessary), then collapse & clean under green.
  • You don't write Ruby code. You write a DSL to solve the business problems you have, then implement it using Ruby. If your business logic looks like Ruby, you're doing it wrong. Look at Rspec - it's a DSL, not "Ruby Code".
  • "Writers write, always".
    • Not sure if what you want to write will work? Write it.
    • Doesn't work? Delete it.
    • Kinda works? Keep what works, delete the rest.


I'll post more on this as time goes by...

Post a Comment

Popular posts from this blog

Agile Performance Management: Why Performance Reviews Suck

Many thanks to Mary Poppendieck, who wrote about this topic in 2004, and proposed a comprehensive solution.  She is the inspiration for much of my thinking on this subject.  She is also a better writer than I am a cartoonist.


Performance reviews suck.  I don't know of anyone who goes into their appraisal without some trepidation.  Your boss is guaranteed spring some surprise criticism on you that is ill-informed or misses the point as you see it.  It's a real challenge not to get defensive about that.

The only thing that makes your own performance review suck less is having to give them.  As a manager, I have dished out quite a few, and some of them went pretty badly.  (To the people at my first management job: Thanks for helping me learn how to get better at them.  Your sacrifice was not in vain.)  Since then, receiving one isn't nearly as gut-wrenching, if only because I try to make it easier for the guy on the other side of the desk.  I've been there, and I know how …

Do. Not. Optimize.

You've probably heard this quote before:
Premature optimization is the root of all evil.
 - Tony Hoare
Speculative optimization is always wasted time.  In the absence of an actual performance problem, you're just burning time that could be better spent on refactoring your code to make it clearer.  This is exacerbated because performance-optimized code is usually harder to read than code which hasn't received such treatment.

Here is what you're doing when you optimize:
Adding code that now must be maintained.Obfuscating the existing code.Spending time writing code that doesn't add value. But what's that you say?  You have the experience and know-how to decide when optimization is needed?  Maybe, but probably not.   The people at Sun and Oracle may or may not be smarter than  you or me, but they certainly know more about optimizing Java bytecode than we do.

For example, some people think that having a large number of classes is slower than the alternative.  This …

Showing Off: How to Do a User Demo

Rather than repeating what has been said elsewhere, here is a nice short post on agile-for-all that covers the basics.

Here are a few things for my own future reference and teams that I'm working with...

Try to keep each demo to 5 minutes or less.   If it's longer than that, it's possible that you should be demoing more than one story.  More likely, you're just being too wordy.

TALK LOUDLY.   No, louder than that.  Louder.  Do you feel like you're yelling?  OK, that's about right.  You need to put your voice in public-address mode for 5 minutes.

Focus on why your audience should care about the story  This is particularly important for back-end work.  For example: Your story generates a feed of XML that will be consumed by another application. Show the output, and point to a couple of salient features in it.  Then be done.

The important part of the above is "show the output."  Showing the end users how to interact with your service is a separate sit-d…