I spent around 10 years of my career writing all sorts of automation - I don't think automation is a good thing

-

I spent around 10 years of my career writing all sorts of automation. Whenever I hear another company working on yet another breakthrough in automation it gives me a bitter smile. Let me explain why. (and it is not another `automation is impossible` rant)

The other day I was having breakfast at McDonald's, where I noticed how few employees they had on shift, yet able to serve quite a few customers. I worked at McDonald's and I remember that cashier work was particularly challenging - usually one had to take orders and prepare orders at the same time, all in 120 seconds 9 (it was in Russia 20 years ago, I might be slightly wrong with figures, but you get the point). A Cashier was also supposed to smile and let you feel welcome.

Now they have self-checkout stations, leading to funny results:

  1. Order preparation is nowhere near 120 seconds. It takes ages now, to be honest.
  2. They employ fewer people. You know, crew members at McDonald's don't usually have a line of job offers to choose from, so they may not appreciate the argument `people could have more interesting jobs`. When they lose a job they may as well lose it for good (or bad).
  3. The bloody machine does not make people any happier. Customers wait longer, employees being let go (or not hired), we have fewer human interactions, which, apparently, not beneficial for mental health and wellbeing
  4. Companies developing, promoting or using this kind of automation don't seem to give a shit regarding the wider impact on society.

I am not against automation per se - automation does not hurt by itself. But I am against mindless tools and profit obsession - while we, in fact, should think what we're going to do with all these shiny tools and nice profits.

Thoughts, suggestions, something?

Comments

Post a Comment

Popular posts from this blog

Test automation framework architecture. Part 2.1 - Layered architecture example

-
Image
Let's consider an example of what Layered (Tiered) architecture may look like for a test automation framework. As a system under test, we're going to use this simple and neat "Todo list" application. First, let's do a brief analysis of the application. From my brief exploration I came up with the following checklist: Area/Group Things to check Comments Todos CRUD 1 Create item Basic scenario, UI-level case 1.1 Create an item with the same name The case is not valid. There's no validation for that - nothing to check really. 1.2 Create an item with an empty/not valid/malicious name While it would be a nice thing to test manually, from test automation standpoint I would expect this to be filtered on service or repository level, so either integration or unit test . 2 Mark item complete Basic scenario, UI-level case 2.1 Un-mark item complete Basic scenario, UI-level case 3 Delete item Basic scenario, UI-level case 3.1 Delete item
Read more

Test automation framework architecture. Part 2 - Layered architecture

-
Image
Probably the most popular architecture pattern used for test automation frameworks (TAF) is layered architecture. This pattern is so well known that on job interviews for some companies when they ask you about TAF architecture you are supposed to describe this one. If you don't - they think you know nothing about the architecture altogether. I suggest you first read a brilliant description of the pattern at the O'Reilly web page , cause in this post I am going to describe the pattern in a way it is usually applied to build test automation solution. Usually, there're three distinct layers, which may have different names, but follow the same logic mostly. Sometimes those layers called test layer , business-layer and core layer , but there're no standard names really. Key rules for layered architecture are the dependency direction (each level depending on the level below) and call direction (no level can call/reference code described in the level above). The rough
Read more

Efficient test automation - Secret #1 | Test Club

-
Image
It seems everyone talks about efficient test automation, but not so many people have actually seen it! To cover this I decided to make several videos regarding the secrets of efficient test automation. Today we will talk about the first (and, arguably, the main) secret - realistic expectations. Very often, test automation projects or initiatives are started with the following unrealistic expectations: "Test automation will replace 'manual' testing" "Test automation will provide fast results and benefits" "Test automation efficiency depends solely on test automation engineers" Unfortunately, all those expectations are not realistic! Watch the video to know more!
Read more