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 - do I need it at all?

-
Image
While there're lots of information published on the internet about how one should develop/buy a Test Automation solution, there's an elephant in the room - which is the fundamental question "Do I need to do it at all?". That is a good question. While I think that there’re some legitimate contexts where product/project/team can benefit from having a sophisticated test automation solution/framework, my general rule of thumb is “If you need a framework - you do it wrong” . There’re at least several decent papers showing the benefit of unit-testing ([1],[2], [3]), while I could not find any research proving that system level tests could bring better results. Please let me know if you can prove me wrong. There’s at least one half-scientific paper showing the benefits of unit tests in comparison to integration/system level tests [4] There’s a good paper bringing a notion of running/writing and maintaining test vs. the benefit of having/running it at...
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

An alternative to ubiquitous UI-level checking - Subcutaneous tests

-
Image
Let's assume a hypothetical situation - you were assigned to a project to help with the "test automation" initiative. You have a huge "test plan" as an input, containing hundreds (if not thousands) of "test cases" and you need to do something about it, quick. Problem statement Your first urge (if it is a Web application) may be to write some UI-level automated checks using tools like, you know, Selenium. In fact, there's a huge demand for such "Selenium test automators" in the industry these days. But please, please, don't do this. There're lots of things which make UI-level automated checking the least desirable approach: UI-level automated checks will be slow. There's just no way to avoid it. You can parallel them or do some other tweaks to speed them up somehow, but they still will be slow. UI-level automated checks will be flaky. Partly - because they're slow. Partly because Web browser and UI interface w...
Read more