I can think of at least one scenario where you need that call center worker. Let's say internet goes down in your area, but you're not sure where the problem is. Allowing a customer to call for a technician to come check the connection in your house might be a waste if the problem is regional. If too many people do that, the waste of resources compound. And you could argue that AI could diagnose where the problem is and choose what to do, but maybe it can't. You need that human to disambiguate the course of action.
Diabetics can eat cookies and ice cream, they just need to shoot themselves with insulin afterwards. It's having too much of it the problem.
Besides, if something is bad for you, you avoid it. Period. There are infinite other flavors in life to make it all about that single one. "But I want it" is not a reasonable argument.
I love it! There are a few bugs though. If I select a set of equipment and proceed until I get the exercises, but then go back and change the equipment, it doesn't seem to update itself.
I absolutely abhor using a dead person's image or material for new material. I don't want to hear an AI Beethoven or read an AI Hemingway.
Actors are the same. Those are not the real artists, just what some corporate shill thought those actors would do. If you enjoy that, understand that it's not different at all from watching an animated movie.
The Indiana Jones franchise exists because of the Indiana Jones character. People that go to one of those movies want to see him.
If you setup a Mary Sue that treats him like an useless geriatric waste of a man, and finish the movie by having this Mary Sue knock him out, you're basically pissing in your own franchise. And since Harrison Ford won't be able to do another one, this is how the franchise ended, with a sour note.
Many interviewers fail to provide enough context and that leaves the interpretation of the prompt too wide open
So do clients/customers. What's your point? That an interview to assess whether a developer can elicit requirements should be less hard than dealing with an actual customer?
So, the new thing is that we're going to call everyone an engineer?
Carpenter -> Wood engineer
Tailor -> Fabric engineer
Ceramist -> Clay engineer
See how dumb it looks? And maybe the field is too new to have a specific word for it, but calling it "engineer" diminishes the level of actual engineers.
Doesn't matter if it can. You'll have to know how to do it too. Otherwise, you'll never be able to recognize a good fix from a bad one provided by the AI.