Guest Mobbing at Emmersion

 A few weeks ago I saw a post on Twitter, asking if anyone would like to join a team as a guest-mobber at Emmersion. Unless you're a contractor, or freelance, then it's not often you get to work with complete strangers, to see how they work, what kind of problems they face, how they solve them...

Anyway, Mike Clement got back to me, and once we'd sorted out the NDAs, we agreed on a two-hour session with one of their dev teams. The slot was right after work for me in Scotland, and early afternoon for them in the US. 

So last night, I joined a Zoom call, and we jumped straight in to solving a production problem. They had a mob of five, with me as well, and their product owner at the start.We were looking at a problem where the user could do some input, the data should be sent off to a third-party, a response received, and then the UI updated. But something was wrong, and it didn't work.

Like a lot us, they had a complex legacy system which none of them understood. It looked like they had started to use a strangler pattern, so some requests went through a new simpler system, and some went on to a monolith. 

Maybe because this was a tricky issue, where the broken link could be in many places (Was it the user input? Was the data not sent to the third party? Was the response ignored? etc) the team swarmed round the problem at first, with different people looking at different bits of code, while one person talked to me. It was maybe an hour in that they started working on code together, and even then, one person seemed to be off doing their own thing until it was their turn to drive. 

But once we had found the problem and poked around at a couple of alternative solutions, we had the problem fixed. We then immediately discovered that the bug had hidden some other bugs that were now reproducible, but it was at least a step forwards, We worked in 7-minute iterations, with no strict navigator. They weren't strict on changing over when the iteration was up either. Several times, people carried on working for a few minutes after the seven minutes was up, which I thought was interesting. On my team, we use a timer that locks the screen, so we are forced to switch when the iteration is up. 

And the final thing I noticed, especially because this was a two-hour slot right after my normal work, was that they didn't take breaks for the two hours. We take breaks every half hour normally, so this was an intense and exhausting experience for me!

Overall, though, I'm very grateful for the team at Emmersion to offer me this opportunity, and I wish them well in the future :-)

Comments

  1. Mike ClementSeptember 3, 2020 at 7:24 AM

    Thanks Barney! The team really enjoyed having you. It's great to cross-pollinate and share ideas on how to improve our mobbing practice. If anyone else out there is interested in joining us, let me know via https://bit.ly/emmersion-guest-mobber .

    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