[scaredginger]

Self-checkout isn't a great example since it's mainly just shifting the work from one human (the employee) to another (the customer), rather than true automation.

As a side note, we were told decades ago that visual programming would similarly displace developers; however, I'm doing perfectly fine

[analog31]

The best thing about self checkout is the parallel stations, so that getting behind a single black swan customer won't set me back by half an hour.

In some cases, shifting work to the customer is a net positive, especially if the customer can estimate their own time and effort better than they can estimate and manage someone else doing it. Nearly a half century after The Mythical Man Month, managing software development is still widely agreed to be an unsolved problem.

The cost of software development is not just the time and effort, but the existential risk to your own job or business from its unpredictability. This is why I do all of my own programming, and also most of my own home repairs... and use the self checkout at the supermarket.

It didn't displace developers because the industry has grown to absorb them. In my own case, I use my programs to get my own job done, then hand the whole thing over to the project team, and the developers write the production code that ends up in the product... but not at my expense.

[psi75]

Self-checkout isn't a great example since it's mainly just shifting the work from one human (the employee) to another (the customer), rather than true automation.

It may not be true automation, but it's very effective, and it's something we're seeing not only at the grocery store. What used to involve calling a person up and asking for services is now done through web portals... taking a few minutes of the person's time.

The real issue in this degradation of customer service is usually not the time cost but the fact that, while it doesn't change the amount of random human error that occurs, it shifts the penalties onto the users... if your travel agent screws up, you get a refund... if you screw up (in something that used to be someone else's job) you're told to eat the costs.

Thing is, the replacement of a process when an ersatz alternative may not be "true automation" but it doesn't need to be in order to work. And job destruction across an industry isn't 0/1. There are still jobs in car factories in Detroit, just far fewer of them. There will still be jobs for truck drivers in 2040, but there probably won't be nearly as many. Employers will still need programmers; they might not need the same number of us. It only takes a dip of a few percent in job supply to cause wages and working conditions to crater (that's inelasticity), and even this says nothing about the ripple effects and systemic calamities (up to and including the possibility of economic depressions that last decades) that occur when large numbers of working people lose substantial income.

[Ekaros]

True automation would be system that would at 100% accuracy note and bill all of the bagged items you carry out of the shop. Without ever scanning them. Which turns the whole thing to much harder case to solve. 90% is simple, but it really doesn't change the last 10% still needing to do essentially the 90% again...

[coffee_beqn]

There’s already Amazon Go which is fully automated

[imtringued]

It is kind of ironic that we use this technology to detect shop lifting at clothes stores instead of just charging people at a turnstyle.

[29athrowaway]

Even better, less money spent by companies, cheaper products due to lower expenses at the retail level.