Programming, Fast and Slow


In 2012, Daniel Kahneman published “Thinking, Fast and Slow”. It’s one of those books that most Agile coaches and thinkers own, but very few have read. Because it’s not an easy read. It’s long, for a start. But it also goes into a lot of economics and psychology which, even for a popular science book, is hard. And it’s a book summarising a lifetime’s ground breaking, Nobel-prize-winning research. 

I read it over several months, and it was difficult. But I was already intrigued by these ideas. My brother lent me Julian Jaynes’ amazing “The Origin of Consciousness in the Breakdown of the Bicameral Mind” many years ago, and the idea that we function in a largely non-conscious way has been rattling around my head ever since. 

The central hypothesis of “Thinking, Fast and Slow” is that our minds have distinct subsystems that work In very different ways. Our conscious mind is System 2. It can reason, plan, learn. But it is expensive. It uses up lots of energy, so our minds avoid using it. Instead, we use System 1, which uses heuristics, is fast, irrational and full of shortcuts. It’s a great first-response mechanism to a complex rapidly evolving world. But it’s rubbish at making good long-term decisions.

When I read the book, I’d already been Mob Programming for a few years, and I knew there was some sort of connection, but I couldn’t put it into words. It’s really hard to think about thinking. 

If you’re driving, and you’ve been doing it for years, it’s System 1 that does the driving. If you’re driving home from work, you can probably do it on autopilot. You’ll be home before you know it. And if someone pulls out in front of you, System 1 shouts out “What an idiot? What were they thinking!”

But, if you come to a shared use junction, where no-one has priority, and pedestrians are allowed to walk across whenever, System 2 kicks in. You’re forced to think, to negotiate, to be aware. 

So, back to software. When I code by myself, I can stick my headphones on and code for hours. I zone out, and get into flow. I’ve been coding for decades, and I can do it using System 1. But System 1 is lazy and sloppy and does things that are just “good enough”. 

But when we Mob, we are forced to verbalise our ideas. To discuss them. To analyse them. We don’t get to just hammer out code. We have to be deliberate. We have to pay attention. And if we don’t, then someone else in the mob does. 

When we code solo, and we come across some badly written code, our first reaction, our System 1 reaction, is often “which idiot wrote this??” That would be bad enough, but System 1 lives in the moment. It doesn’t consider end-users of our code, or people that will be reading and maintaining our code. 

Deliberate practices such as TDD can help with this. They help to create high quality, maintainable, readable software despite System 1. 

But when we Mob, we engage System 2. We can empathise with people who wrote the code. We have a copy of Norm Kerth’s Prime Directive up in our mob area:

"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."

And we get to remind eachother if we forget. That interaction helps us to empathise. And we are also better-places to empathise with our end-users, and with the people who will have to read and understand our code. 

Empathy

Mobbing encourages deliberate interaction and discussions about our code. This engages System 2. This in turn allows us to empathise more with the people who interact with our code and our product. 

We want our end-users to be able to use our products without thinking. Without having to engage their System 2. We want other developers to be able to read our code without having to think too hard. We want to reduce the cognitive load of the people who interact with our software. And the best way to do that is for us to activate our System 2 now, to write better software, and help others in the future. 

We empathise more when we are mobbing. We write better code when we are mobbing. We write empathetic code. 

Comments

Post a Comment

Popular posts from this blog

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 to B
Read more

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

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 not naming things in our code, by
Read more