Instant Legacy Code

When we ran our recent Coderetreat, one session I really wanted to try was one I picked up from a workshop I did earlier in the year with Kevlin Henney and Jon Jagger. The basic idea is to show people how quickly you can create Legacy Code. 

We had a 45-minute session. For the first 20 minutes, we asked people to pair up, and solve Conway’s Game Of Life from scratch, with no other constraints. 

But 20 minutes in, we asked one person from each pair to stand up and move to a different partner, and carry on. 

Then, five minutes later we asked the other person to move as well to a different partner again, and then carry on solving the problem. The code they encountered was only 25 minutes old, but everyone found it incomprehensible and convoluted. 

We discussed it at a retrospective afterwards, and people were quite angry at the code they encountered, and at the people who’d left it (who were in the room with them!). And they felt guilty about walking away from such low quality solutions and handing it over to someone else. Emotions in coding are fascinating :-)

Because people were using personal laptops, we wanted to make this a safe session. We were using Cyber Dojo (https://www.cyber-dojo.org), and each session has a six-character hash in the URL. We made a note of each hash, and left it on the table where the code was being worked on. Then, when people moved, they could take their laptops with them, and pick up the new URL, and thus the new code, on their new table. 

And this opens up a new possibility. Maybe we could swap URLs with another city during a Coderetreat! 

Comments

  1. garekNovember 18, 2019 at 1:46 PM

    "...people were quite angry at the code they encountered...And they felt guilty about walking away from such low quality solutions and handing it over to someone else"

    This is fascinating indeed!

    It showed me the problem under another angle, though. I think everyone of us have found them selves on either side or on both at the same time.


    Thanks for the article!

    ReplyDelete
  2. UnknownMay 4, 2022 at 1:16 PM

    This comment has been removed by the author.

    ReplyDelete
  3. UnknownMay 4, 2022 at 1:17 PM

    Ooh yes, this is a great idea!
    @ClareSudbery

    ReplyDelete

Post a Comment

Popular posts from this blog

SoCraTes UK 2024 trip report

In September 2024 I attended my second SoCraTes conference, and once again, it was enlightening and fun. There are two formal parts to the conference - a training day, and then two days for the unconference. I say formal parts, because there are plenty of informal sessions as well. One of the great things about SoCrcaTes is that we all stay at the same hotel, so there is loads of opportunities for social interaction. You meet people at breakfast, you maybe go for a walk with other people, there are board games and music sessions in the evenings... It's a strange mixture of really intense and very relaxing! There's a lovely Italian Garden at the hotel, which is a very nice place to sit and chat: SoCraTes has a pretty strong XP focus, but there are plenty of non-technical discussions and workshops too.  The day before This year, the conference was at Milton House Hotel just outside Didcot in Oxfordshire. So on the day before the conference, I took the train from Edinburgh to Lon...
Read more

We always start from where we are

Image
Earlier on in this year, I had a really interesting discussion online with Duncan Hothersall about Scottish Independence, and Brexit. I support independence, and Duncan very much doesn't. Scotland is currently about evenly split between supporters and opponents of independence, with a small number of hardcore unionists and nationalists on either side. But many people are in the middle, and weigh up the decision based on the perceived pros and cons. In itself, this disagreement between Duncan and myself is interesting. We share a similar world-view and similar hopes for the future. We agree in many ways on the kind of future we would like to see. But we disagree on how we want to get there.  This is of course a common pattern. We often share a purpose with other people, but we disagree on the tactics or maybe even the strategy for how to achieve it, and there is a wealth of literature on how to resolve such disagreements.  But what I found fascinating was how we both responded...
Read more

Naming things and Cunningham’s Law

Naming things is hard.  Naming things is very hard.  And, in software, we often want to name things when we know least about them. We create a variable that we plan to use later. What should it be called? How should it be used? We only have a vague plan at this point. And plans, of course, can change.  In my mob, we sometimes struggled to name things. And we would then fall into long discussions about what to call a variable. This often felt like bike-shedding, but we wanted a good name, so we carried on talking.  Then one day, we came up with a new plan. If we couldn’t name something within ten seconds, the person at the keyboard would just hit the keys at random and produce a gibberish name.  We would then use this unpronounceable name in the code, and move on.  And, as we moved on, we would have to talk about the unpronounceable thing. So we call it by what is was doing, by how we were using it. And, often, the name would then become apparent.  By ...
Read more