Calling Me Names — New Labels

After a one year break, I was back to the Agile Testing Days this year (2019). Damian Synadinos gave a great keynote “More Than That“, where he explained, that we are more than ‘just’ testers. We can also be: parents, programmers, trainers, musicians, comedians… The list is long. This got me thinking about labels and titles I’ve put on (or used) myself.

In another talk Tobias Geyer shared his thoughts about wizards & witches (from Terry Pratchett’s series of novels about the disc world) in “Wizards, Witches and Testing” and in it he compared the witches and wizards of the disc world to testers and programmers. Given this input, I clearly identify myself as a witch.

During the breaks, I kept thinking about which labels I could put on myself, especially some that may be a tad bit far-fetched: Since I have some bits of high-tech implanted in my body I could be labeled as a cyborg, technically.

Following a similar thought: If one consumed blood of other people, that make one a vampire. And I did, during an operation last year, I thankfully received a transfusion.

Hmm, a vampire cyborg. There must be more positive sounding labels!

Then, there was a “AgileTD Late Night Talk Show” hosted by Daniël Maslyn. I was invited as a guest to speak about my cancer treatment I went through during the last year and a half. Daniël labeled me as a Jedi Knight, for having gone through this. Thank you! “Jedi Knight” — that’s a label that sounds much more positive! 🥳

"IT DEPENDS" Certified Practitioner

Also during the conference, I became a certified practitioner of “It Depends”, thanks to the exam by Gitte Klitgaard. Very nice, too!

And just after the Agile Testing Days, I took and passed the exam to become an  Agile Testing Fellow

Other than that, since 2013 I occasionally become SuperAgilePerson.

A tiny part of @Stuartliveart‘s sketch note from Agile Testing Days 2015

Let’s combine all those labels:

Cyborg Vampire Agile Testing Fellow
It-Depends Practitioner SuperAgilePerson Jedi Knight Witch

Oh, what a title! I won’t use all of those labels all the time, certainly not on a business card. 😉

What are your labels and titles?

Looking for a New Project

Exciting times: It’s time to find a new project!

What I’m looking for is a role as a software tester in a team that really strives to improve on agile techniques in both, testing and programming. I’m interested in learning more about DevOps, continuous delivery and automation, including but not limited to test automation.

What I’d prefer is a project, that allows — or expects — remote work. Travelling in Northern Germany or Denmark every other week is fine.

Technically, a project using Ruby and/or Rails would be fantastic. In case the team is working on steps to also use Elixir, that would be a bonus.

A caveat: My availability in November is limited, due to a keynote I’ll give at the Agile Testing Days.

More about my previous work is available over at ‘work with me‘ as well as on my Xing profile.

Agile Testing Days 2019: A Keynote

I’ll be giving a Keynote at the Agile Testing Days 2019 in Potsdam, Germany: “Being Lucky”.

Stehpan's Keynote at ATD: Being Lucky

Here’s the abstract:

Good fortune can be influenced, so let’s do it.
Do you think a little more luck in your life could help?
Someone at the Agile Testing Days once noticed that I seem to be a particularly lucky person. This made me ponder: Am I lucky? When? How often? Where? I also asked myself, whether it’s possible to influence luck.
Episodes, some from this very conference right from the beginning in 2009, illustrate how luck can strike. However, it doesn’t necessarily feel like a lucky moment at the time it happens. It may actually feel embarrassing and stressful. These stories also provide some heuristics to help you become more lucky.
Lesson learned: While luck can’t entirely be controlled, it might in fact be shaped in our favour.

Docker’s ‘docker stats’ & names

This is mostly a technical reminder to my future self and a selection of the tips from a proposal I found at https://github.com/moby/moby/issues/20973. 😉

When using Docker, now and then I need to keep an eye on the run-time behaviour of the Docker containers. To do this, there’s a nice docker command:

docker stats

How ever, in the current version (17.05.0-ce, build 89658be), the containers are listed using the container ID.

I find it much easier to use the container names instead of the IDs, so here are two ways to display them:

  1. On an environment I don’t control (a colleagues machine when pairing, a test environment…) there’s a way to change the display of ‘docker stats’ for a single use of the command:
    docker stats $(docker ps --format={{.Names}})
  2. On my machine, I like to have this all the time, so I edited ~/.docker/config.json and added the following key-value pair:
    "statsFormat": "table {{.Name}}\t \
    {{.CPUPerc}}\t \
    {{.MemUsage}}\t \
    {{.MemPerc}}\t{{.NetIO}}\t \
    {{.BlockIO}}\t{{.PIDs}}"

    (The backslash at the end of the line indicates the the line is actually continuing.)

Word of the Year 2017

As before (see 20162015 and 2014) I’ve picked a Word of the Year.

During the past few weeks since the Agile Testing Days 2016 (see my posts Agile Testing Days 2016 — Part 3: Tutorial Day 1Agile Testing Days 2016 — Part 4: Conference Day 1Agile Testing Days 2016 — Part 5: Conference Day 2Agile Testing Days 2016 — Part 6: Conference Day 3 and Agile Testing Days 2016 — Part 7: Unconference Day), I had a few ideas about what to kick off in 2017.

Actually implementing some of these ideas will require some development, in various meanings of the word. So that’s my guiding word for 2017:

word-of-the-year-2017-develop

With a few lines from a Xavier Rudd song, let me wish you all a great year 2017:

Well, I wish you well on your journey
I hope your dreams they come alive
I hope your dreams back down and they, they thrive
I hope your dreams they come alive

— Xavier Rudd, “Shelter” from the album “Solace”, 2007

 

%d bloggers like this: