Saturday, April 18, 2020
Doozy! Only two bugs left.
Saturday, March 21, 2020
Bad luck !
According to the table below(published by the New York Times [1] today on March 20), New York has almost 7 times the amount of registered infected Corona patients compared to Washington but "only" about 0.5% of them have died so far.That's quite a good quota (for Corona). Let's have a look at the other side of the continent. The Corona deathrate in Washington is nearly 6%. That's quite a contrast. What can be the reason for this difference? In most other States the mortality rate is roughly around 2%, similar to other countries in the world.
Here are some superficial (not seriously meant) hypotheses:
Let's get more curious and read the full article. We find valuable information by reading the details and then very quickly understand what happened. It is noted that 2900 of the reported cases in New York were all registered at the day of publishing the numbers. Interesting, probably it is too early for those new cases to "die". If we ignore these new cases (7102-2900), we still have a quite good quote of 0.8%. Better than in many countries worldwide. But further reading the article reveals “At least 35 of the deaths were connected to a single nursing center in Washington" and "...many of those cases involved older people with other health problems that made them especially vulnerable to coronavirus”.
- The New Yorkers are doing something extremly right and those in Washington are doing something extremely wrong
- The dirty air in New York is poison for the virus. The more CO2, the better for human beings. Bad news for Greta Thunberg.
- New York may not be a typical state for eldery people to relax...,probably more young and healthy people live there while in Washington may be a pan of sick or eldery people spend the rest of their lives there (again, this isn't meant seriously, okay?)
- New York was better prepared for this predictable disaster
- or...the measures may have been taken inconsistently and/or the numbers are simply wrong
Wednesday, March 11, 2020
Corona
Basel carnival cancelled, soccer games cancelled, business trips
cancelled, Swiss Testing Day conference cancelled, borders closed and
today it was announced that all flights from Europe to the States are going to be stopped by end of this week. WTF. My friends just managed to catch a plane to New Zealand...probably one of the last ones. Will they be able to catch a plane back home to manage their big farm in the Engadina? Everyday another employee is missing in our offices because he/she either feels sick or is afraid to feel sick soon. It's a weird silence. Those who dare to cough are potential suspects. Even worse if you fetch a handkerchief.
If you had predicated all this 2 weeks before, I had sent you to the psychiatrist to help you return to reality. Well, this has now become the new reality and that's why I feel baffled...where does all this end? Either, the whole racket goes up in smoke very soon or...yes, or what? Can't really think of any alternatives. It's a situation we never experienced before, hence whatever is decided probably can't be so wrong. It's all new, we are learning. We are learning to deal with a worst case scenario and we are likely to pay a high price. Can I go on a summer holiday and have aswim in the Sea this year? Will we lose money if we book anything anywhere or do we have to stop planning at all and instead live spontaneously? Will I be trapped behind closed borders? Will my family fight for food soon? People living in war zones would still envy me for my comfortable situation. So it's not a worst case scenario yet, maybe just not a very funny one. What happens after this is all over? How many people will lose their jobs because their company went bankrupt or because the company is forced to tighten their belts. Spooky.

What shall I do? Drawing is a nice therapy...and while I am doing that, I am listening to Dave Grusin, Grover Washington, Fourplay, The Rippingstones, Earl Klugh, etc..how great this feels at the moment. It's my drug to disappear into a different world, at least for a short moment in time. I need it right now.
And tomorrow, I am having a beer with a good friend.
P.S.
Add on as of March 21: In general, this is a blog about software testing only where I put my cartoons and enrich it with explanatory text, but sometimes, I am inspired by things that happen outside the world of testing, like Corona for example. My brain is currently full of cartoon ideas related to Corona. Since I don't want to deviate from my testing related cartoon strategie, I have decided to simply put all my Corona related cartoons into this particular blog entry rather than to create a new entry for each cartoon.
Thursday, January 30, 2020
404 caused by clumsy whales
I didn't have to change too much. I took it almost 1:1. Check yourself below.
Further reading on a real whale who got tangled:
https://www.newscientist.com/article/mg23231000-400-hacker-the-humpback-whale-who-got-tangled-in-an-internet-cable/
Wednesday, January 1, 2020
The Demo Effect
Originally, the text was "wait until the sprint review is over, then let's go out and show up again", but the scene is less funny with the previous text. The current one turns this cartoon into a more common situation, aka. the demo-effect.
The original text has its root in a real story. Long time ago (not in the company I work right now), the product owner regularly moved all reported defects to a low priority heap shortly before the sprint review, only to put them back into the next sprint right after the review. The goal was to shine with a good product having non-important bugs. With this approach he kept the release manager quiet, because the release manager was looking at high priority bugs only shortly before the review. If there weren't any left, the product owners were out of the line of fire.
It's like in Patriot Games, where the secret armed forces in the desert knew exactly when the spy satellite flied over their hidden military camp. They tided up everything shortly before it reaches their coordinates and then they rebuilt the camp after it had passed (until next time). Result: pin sharp satellite images of unsuspicious cabins in the desert.
Thursday, December 26, 2019
Robots slacking off
Dear readers,this is very likely my last cartoon for 2019 and I am already looking forward to drawing and publishing the next ones in 2020.
14 cartoons in a year is not bad, considering the fact, I have hardly any time to settle back after work and after having helped kids for school.
For those who want to know, I have a quite consistent hit-count on my blog (1600 pageviews p. month). In my world this is a lot. Well, not enough to become famous but still a lot of reasons to continue drawing in 2020. I wish you very XMAS (even though I am kind of late) and a happy New Year 2020.
Torsten J. Zelger
Sunday, December 8, 2019
False Positives
When developers want to quickly demonstrate that in principle it works, they tend to hard-code things with the intention to replace that piece of code later. But, once it works, the focus is shifted to other tasks. It is likely that one forgets about these rotten code pieces.
When Switzerland changed their tax rate from 7.6 per cent to 8 per cent, we were quite surprised that 7.6 was hard coded rather than read from a configuration file. As a result, we had to redeploy a new fix. In another example we found a code statement that made the program wait for 200 seconds. No wonder the application was slow. The developer had a good explanation why he added a wait-statement, but he mixed seconds with milliseconds.
The term "false positives" has its roots in medical testing. A false positive is an error in which a test result improperly indicates the presence of a disease (the result is positive), when - in reality - it is not present, while a false negative is an error in which a test result improperly indicates no presence of the disease when in reality it is present.
Simply said, never trust any success messages. If the program claims it worked, the program may be wrong. Vice versa is also true. When the system throws an exception, the operation may still have worked correctly, regardless of the error.






