A tweak to faster development.

It was a yellow wooden schoolhouse that housed only a 100 pupils. I went through the entire elementary school in this idyllic setting. A small town boy, would someone say.

Image for post
Image for post
My school in Kemi, Finland. I guess it was around 1988.

On third grade, we started on our first foreign language. It was English. In the first class, we came up with English names for us. I was ‘Andy.’ My friend Aki was a big fan of the ‘Jake and the Fatman’–series, so he wanted to be ‘Jake.’

We always start with the vocabulary when learning new languages. And pretty soon we move on to phrases and the first dialogue practice with a friend.

‘Hi. My name is Andy.’ I said. ‘Hi, Andy. I’m Jake’ Aki replied.

We learn quickly in dialogue because we receive a fast feedback from your friend.

But what if we moved this exercise into a software project? The coder makes a change commits it to the version control. A sprint passes. Or a month in a more classic setting. Then a random tester takes it, and the coder finally gets a response. ‘Jake. How are you doing?’

Considering learning, who would benefit from such a dialog? Or thinking about fixing bugs.

Do you still remember what you did two weeks ago at this time? Or a month? I don’t, and neither do most of the developers.

Digging into the human memory has an implication. Recalling and reworking what we did weeks ago takes a lot of time. And that time is away from building new things. And the risk of mistakes we call regression grows as well.

A flowing dialogue between developer and tester will produce the results that you seek. Faster development with fewer bugs.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store