December 14, 2009
Last week, the Swedish ALT.NET group hosted an experimental Code Sparring night at the RemoteX offices. The idea came from the experiences we’ve had with coding dojos and the problems we recognized with that particular way of evolving as a coder. Mainly we felt that there was too much idle time for the people not sitting at the computer, and things quickly became messy with complex communication behaviors disturbing the overall experience. So I suggested that we should work on programming challenges in pairs instead.
Sparring in martial arts
There are many metaphors for software development taken from the world of hurting other people, and this is no different. I have some limited martial arts experience, mainly MMA, and I’ve always found that the most rewarding part of practice was the sparring.
A sparring session usually consists of people pairing up to try out their skills in a slightly more realistic environment that is still safe. The sparring may be very broad, i.e. everything is allowed, or sometimes only a subset of techniques can be utilized or you have to accomplish a specific goal (such as a rear naked choke).
A boxing class, for example, might start off with warm-ups and then move on to technical drills, such as a improving hand-eye coordination, like the guy to the left, or specific striking combination for 30 minutes. After that, you could finish with 30 minutes of sparring. The sparring is usually done in pairs, and you go at it for a round and then change your sparring partner. The goal is of course to improve and during the rounds you learn from each other, help each other and get to apply fine-grained knowledge in a complex and fluid situation.
How well does it translate to our profession?
Very well if you ask me. We can say that learning the programming basics through reading books, attending courses, practicing katas etc. is like drilling, and our day jobs are like a real fight in front of an audience. So code sparring should be something in between that is safe (e.g. you wont harm any important production code) and less competitive/dangerous.
I know that Micah Martin has a different definition of what code sparring is, but that was a sort of competition instead of what I feel sparring really is. I’m not saying that it’s a bad thing, but I’d call his version “light contact coding” or something.
Anyway, to emulate real programming work more than a dojo did for us, roughly 10 people gathered at a big table and paired up. In order to keep things fluent, fun and to learn to know each other better, we rotated every 20 minutes. Due to the fact that people might feel uneasy about the prospect of handing over their sacred computer to others, the ones who brought laptops stayed put, and the others switched seats by moving one step to the left. The assignment we chose to work on was the KataYahtzee, driving the implementation out using test-driven development.
The people who rotated always had fresh and clever ideas from the other pairing stations they had been at (just like consultants, eh?) which merged together with the existing code to evolve into something new. And constantly being part of a pair meant that everybody seemed to be focused and utilizing the time efficiently from start to finish. Also, unlike a dojo, any group size should work for this kind of exercise.
The constant change of pairs also meant you had to be able to quickly communicate the whats and the hows of the code to your new partner, which sharpens your verbal skills as well.
The biggest problem that I could see was the strict division between the laptop owners and the more consultant-like people who changed code base every 20 minutes. Some people were not content with sitting in the same seat all night, so there’s room for improvement. Make sure to read Morten Nielsens summary of the sparring as well.
Why don’t you try a code sparring night in your office or with your local user group? If you do, tell me how it went and any suggestions you have for making this better.
EDIT: I am in no way claiming that I invented this kind of practice. I know that CodeRetreats are very similar and other kinds of pairing roulettes existed before I suggested Code Sparring.
August 6, 2009
I just found the video of my lightning talk on object databases for .NET. It was recorded during the February 2009 ALT.NET Unconference in Stockholm.
Thanks to Petter Wigle for recording, editing and putting it up on Viddler.
Edit: I’ve been told I’m looking back at the slides projection way too much during this presentation. I agree. It’s because someone changed the settings on the laptop just before my presentation, so that I couldn’t see what slide I was on on it’s screen.
November 25, 2008
The fear in the .NET community of alternative tools, especially open source ones, is doing a lot of harm to us. There’s a paraphrase I learned from the ALT.NET movement that goes “No one ever got fired for choosing Microsoft” (I think the original quote was about IBM). And it certainly feels like it’s tragically true, the fact that we only trust Microsoft to provide us with everything and that nothing trustworthy can come out of the plethora of excellent ideas and tools that exist outside of Redmond.
Whenever I hear about this, I think of a person I talked to once. This person was going on and on about this open source version control system and how much it sucked, how they had never been able to get any support and how it showed just how rotten open source products are in general.
Curious to know, I asked the person what system it was. The answer I got was “SourceSafe”.
Of course I had to tell this person (not a developer mind you, but working in a .NET developer team) that it’s not open source software, but rather some crap that Microsoft has produced.
It’s an amusing story, and is serves as a good example of how many people working with .NET seem to feel about Microsoft vs open source.