Delegate report about CITCON 2017 Amsterdam

“We did it already 14 times.”
Jeff paused for a moment,  “and this one was amazing.”
He was quite modest.

Gotta attend this 1

A few months ago a speaker told about his experiences at a conference. He had difficulties to make contact. One of the responses intrigued me. Mohinder Khosla mentioned CITCON in Amsterdam.

For a Dutchman this was interesting. The price was also reasonable 0 Euro with a modest request to cover the costs. But how could I determine whether the price was right? Among the participants I noticed Gojko and Cirilo. Wow. Then I read a recommendation of @testobsessed and I was sold. I mean the ticket.

Not bad for a conference with a marketing budget of 0 Euro.

Evening 1

Before I want to describe, what happened, I have a small warning. This post will focus on the process and not on the content. The reason I chose to is simple: people came there to share information and difficult situations. So reader beware.
Now it is my task to draw you in the atmosphere of CITCON 2017 Amsterdam.

The first day I used public traffic to go to the venue. It was hosted by Xebia. This office had all the elements to affect people’s mood. There was a standard meeting room with glass walls, a comfy corner including sofas and game computer. Did I mention the TV? There were rooms where I could see concrete shining through.

Evening 1 started awkward. I only knew one participant and he was not present, so I talked with new people. The talks were friendly with a formal undertone. Really polite. Just probing around.

Jeff and P.J. started the conference in a room with more than 100 seated people. They casually introduced the format. Asked for feedback (“5 stars is good.”). And let all participants introduce themselves and telling about things they were excited about or personal struggles. Those small stories let me connect to the people telling them.

The subject proposal session was described. At the moment everyone felt at ease P.J. and Jeff told, that they would take a step back. They would only help in case of problems. It was “your conference”. This lead to an extension of the Q&A. After the last question the organizers withdrew from the flip boards. It was up to us, the delegates.

After the warming up the real stuff started people were requested to pick a subject and clarify it to the audience. A queue formed in the room. People with posts its interested in solutions or volunteering to share information.

I watched the process for a half hour and I noticed the time. Time to send text message to my family, that I would come home later.
I really liked the way, how the subjects were presented. The question part was really clarifying. Participants tried to understand the content. The atmosphere had changed: it was warm and people were supportive.

Let me give an example. I proposed a session to share information about blogging. For me it is a way to clarify my thoughts and reflect. I was questioned about it:
“Why do you call it ‘Blogging as a service’”?
“I needed a title … and it is a service to the Community and outside the Community.”
BTW there was also a session proposed “What’s in it for me?” It was listed In the final program.

After the subject proposals I voted and went home. Afterwards I heard from a fellow Dutchman, that he was requested to compose the program. He kindly declined. He had already arranged the venue. This was a reasonable excuse.

Morning 1

The next morning I entered the office, where I had a small chat with Pati about conferences and IT. I skipped my second breakfast and collected a good coffee. There was a friendly buzz in the air.

I went to the program and browsed through the stickies on the flip boards. My session about blogging was accepted. Yay. Then the bad news sank in: there were too many interesting sessions at the same time. That happened to me years ago.

I arrived early for the first session. I remembered that several stickies or subjects were combined. The room was quite big for the small group. I moved my chair to the middle of the room for better interaction.

The first session was about testing and I tried to participate as good as possible. I had to watch my politeness, but I had no time. The subject was too interesting. I bent slightly forward and started contributing. I was in business mode: polite and helpful.
The day before the code of conduct was explicitly mentioned. Proper use of language was also checked :
“Can I use the F word here?”

For the second session I had to find the stairs. Glass walls wrre exceptionally handy in this particular case.

The previous session was still in full swing. I put me in the background, while observing the room. Sofas. These are great: It is difficult to maintain a neutral position. So I had an extra indicator for inclusiveness.

So I was in my session about blogging. And someone else. Okay time to start the Q & A. There were good questions. I got other questions than expected. Those made me think and reflect on my actions.

After a while other people joined. They had used the Law of Two Feet. If delegates were not interested in their session, they were allowed and encouraged to change the session. For my session it was welcome.

Lunch 1

During the lunch people were still having sessions. One session was about strange effects of particular Unicode on programs. A bit too tech for me.

You might have noticed that I changed the category to ‘Techies conferring’. My first thought was, that CITCON was about testing, until I read the description. It was about integration and testing. Other technical people would also be present.

During the lunch I joined a conversation about 3,000 pipelines. This was another world for me. So I had to drop my idea of an extremely small set of pipelines. There can be more than 1.

In a later session “mister G” had a good suggestion to improve builds. Suppose you have suppliers who are only focused on their own software. “Just let them provide tests to each other they can use in their build. If the build breaks they have something to talk.”
G thanks.

Writing about the afternoon let’s switch sections.

Afternoon 1

After the section switch I try to stay of content, but that is difficult.
One participant told a story about switching lines in code in order to cause bad unit test results. If the unit test did give an OK, there was likely a bug in the unit test.

I also saw some really awful Gherkin to describe actions instead of abstractions. Gherkin is good for testing of flows. For tabular stuff FIT of Fitnesse are the tools to use. And Concordia is another good option for the remaining option. Thanks Gojko.

For one of the final parallel sessions people were requested to bring real life testing problems. I joined this session. The facilitator did a good job to clarify the problem. A lot of whys and whats. I thought I could handle a lot of testing problems, but these were really hard to solve.

O yeah. Back to the process. I went to a big meeting table and met someone else. After some small talk we decided to start. About …
I volunteered to take a picture of the stickies. My hand went to my pocket and stopped. The location had been changed. I had been warned. So I warned the other and up we joined the session in progress about Gherkin. You might have read about it. Some centimeters higher.

After the session everyone was gathered in a room to share their AHA moments. There were a lot. I saw people who showed emotions. I saw people ready to take action when they would be back in the office.

People referenced to the ‘Gentle punch in your face’ session with Jeff. Other people had some great conversations. Outside in the sun. Hopefully a dev snd a tester. The truce is out there.

Evening 2

With more than an hour travel time and past my dinner time I had to find some place to eat. “It always works out.” Jeff reassured the people. Indeed a big group assembled on a terrace enjoying snacks, French fries, and burgers. They even had veggie ones.

I talked with other testers, who knew about context driven testing and cynefin. I don’t meet these testers very often.

There was a friendly guy with a nice sweater with a known software supplier on it. That made me curious:
“How did you get that sweater?”
“I work there.”
“I use your software.”
“Me too.” another techie joined in.

I ended in a group of Finnish guys. Talking about things. Things different from IT and work.

Thanks P.J. and Jeff for the conferring.

Pizza dough though

One of my kids read the recipe.
“Now we need salt. So I take the Baker’s Salt.”
And I had to switch gears: Baker’s Salt?!

For a starter …

On my days at home my wife hands all the cooking stuff over to me and I have to figure how to cook, grill, or bake. In my family weekend starts on Wednesday. My wife and I puzzle about the meals.
One of the no brainer recipes is pizza. I thought.

My wife was still collecting recipes. It basically meant, that I had to sift all kinds of papers. I already used the pizza dough recipe a few times, so I could tell the basic characteristics: white paper with a eightsome steps.

I browsed through the recipe folder: nothing.
I opened the Baking Bible: niente.
My kid was thinking all along the way.
“Let me have a look at the folder.”
Again: nope.
Then I remembered a book written by a national known baker. My kid had enough information and retrieved the book with half centimeter stack of recipes: bingo.

The next course is …

Next step to the dough was machine assembly. I put the machine on a comfortable place and picked the K-beater. Yep, that thing in the picture.  I still remember my first impression of this part. there is a K in it. When my wife mentioned the K-beater …

All parts were fixed. Now I needed the ingredients. My kid helped me measure the water and the flour:
“We need to use the patent flour”.
I agreed.
I was proud to remember to put the water first into the bowl. My wife had stressed that several times.

Then Baker’s Salt had to be weighted. A special spoon with a built in scale was used for this purpose.
“That is little.” I heard.
Before I could help: “It was 0.3 gram.”
I heard nothing more, so the accuracy problem was handled.

Then I wanted to add the Baker’s Salt to the water and the flour. But my kid was determined: it had to be added later on. OK. But we still needed the yeast.

My kid picked a small plastic cap out of the drawer.
“The salt and the yeast must not be mixed.”
The cap was placed in the spoon and the scale was reset.. Then the yeast in the cap was measured and added. Oil was also added.

Then it was time for me to start mixing. After a minute the salt was added. The K-beater had a heavy time, so I switched it after a small consult with my kid. Imagine a dancing kitchen machine. Not funny. So I used a new part. It looked like the left hand (?) of Captain Hook.

After 18 minutes I got the dough out of the bowl. My kid made a circle in the air with two hands:
“Mom always does this.”
“Can you show it again?”
The movement was a few times repeated. So I gently moved my thumbs over the ball of dough. My kid was not content. The ball was pcked out of my hands and placed on a kitchen cupboard. Then the ball was firmly cupped with two hands. The shape looked familiar to me. Nice touch.

I then let the dough swell.

For dessert …

“The pizza bottom is crispy.”, my wife remarked.
I bit and agreed.

Some people might have noticed that I did not use any computer related word. Except the bolded one. Let me continue.

My point is of course related to my profession. It was not about looking beyond the instructions neither about using knowledge in practice. This story is all about cooperation.

DUMB heuristic

During the Rapid Software Testing course James Bach advised to name things. If I cannot tell, what I am doing, my boss would think: “What the < beep > is he doing?”
So after the course I came up with the DUMB heuristic. This heuristic I use frequently during my testing.

Suppose my boss asks me how the testing goes. My answer could be: “I do uh my best.” A busy tester is always good, but if I am too busy things might go wrong. All my energy and brain power are focused on the work at hand. I forget to think. That’s DUMB.

When I figured out my heuristic, I had to find some smart explanation for this abbreviation. It became Do Uh My Best. Most heuristics are acronyms or lists of words. In turn every word is explained in detail. You know: turned upside down and shaken. But I just stick to the abbreviation.

Some readers have a good reason to ask. So hold on. The emphasis of the heuristic is on Uh. This is an alarm bell. Hesitation is a sign, that too much is going on in my head. I might forget to pay the deserved attention to the real problem.

This following discussion I had several times with my scrum master:
“I am writing test cases.”
“Why do you make test cases?
How often will the tests be executed? Who will maintain the test cases?”
So I was doing my best. And my scrum master got an Uh out of me.
He let me reflect on my work. What was I doing? And why?

Many test heuristics I know are acronyms. Some I do use. The S in SFDIPOT stands for Structure, how is the application under test built? So which components do I have to test? Etcetera.

If I apply this to DUMB then I would get things like: Do is the activity I am involved at that moment. It can be taking notes in my test charter or just thinking. Etc. Etc. The only thing I need on that moment is a short reminder to reflect on my work. DUMB. One syllable. Keep it sweet and short.

When do I use this heuristic? If there is a lot of work to do. When I have hours of straight testing ahead, I can go in my little cocoon and do something testy and something nice comes out. Tadah.

What about the focus and defocus stuff? Most of the time I use this when I got stuck. What can I do now? Let’s take a step back. Now I see the big picture. I figure out at a high level. Let me zoom in.

The point is, that doing my best is equal to doing stuff which is in front of my nose. I just pick it up and start running. Maybe I get it done today or this morning. Completely forgetting to ask for the reason. And that is DUMB. NOK?

When I was writing this blog, something hit me in the face. That was my imaginary hand palm. This so called heuristic is maybe already known under another name or in another way. Like a proverb.

And yes Madam within a few minutes the following proverbs came in my mind:
Eile mit Weile
Dépechez lentement
Easy does it

A day later followed by
Haastige spoed is zelden goed.

So why am I not using proverbs to keep my testing right? It is too long. Maybe a short heuristic could be useful.

“My scrum master would say something like Does it help?

This is really STUPID which stands for Some Thing …. I Do. UP are two words, so ….

Do I have to figure this out? WHY?”
“We Hear Yes.”

 

 

 

 

 

 

 

 

 

 

 

 

 

“GIRLS”
“Good In Real Life Software”

 

 

“GUYS”
“Graphic Userinterface You See”

 

 

“PLEASE”
“People Lik E A Software Errooor”

“CHEERS”
“Co Herent Entertaining Erroneous Random Synthesis”

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

So you are a mindful reader. Congrats. Here is the bonus.

Why did I not throw this blog post in the waste bin? People already thought about it and distilled their experiences to proverbs.

It is about my thought process. I do not want to stop thinking. Once in a while I discover that other people already have figured it out. Sometimes I find something new. But apart of discovery of new thingies it is about thinking thingies through. Getting better to verbalise my thoughts and explain them to you the reader.

That was what I forget a while ago. Thanks for the attention.

Optional reading Also Known As scientific stuff for nerds like me
When I Do Uh My Best, System 1 is operating. More information about System 1 can be found in this blog post.

WYSIATE stands for What You See Is All There Is. If I am too busy, I forget to look for other relevant information as mentioned in Thinking Fast and Slow.

The Lindy effect is about using knowledge especially from books. Thinking Fast and Slow is quoted for years by some testers. If a book is relevant for 5 years, it will probably remain relevant for another 5 years.