Andrej Karpathy

If we think of tasks as, you know, not jobs, but tasks, kind of difficult definitions.

Because the problem is like society will refactor based on the tasks that make up jobs compared to what's based on what's automatable or not.

But today, what jobs are replaceable by AI?

So a good example recently was Jeff Hinton's prediction that radiologists would not be a job anymore.

And this turned out to be very wrong in a bunch of ways, right?

So radiologists are alive and well and growing, even though computer vision is really, really good at recognizing all the different things that they have to recognize in images.

And it's just messy, complicated things.

job with a lot of surfaces and dealing with patients and all this kind of stuff in the context of it.

So I guess I don't actually know that by that definition, AI has made a huge amount of dent yet.

But some of the jobs maybe that I would be looking for have some features that I think make it very amenable to automation earlier than later.

As an example, call center employees often come up, and I think rightly so, because call center employees are

have a number of simplifying properties with respect to what's automatable today.

Their jobs are pretty simple.

It's a sequence of tasks and every task looks similar.

Like you take a phone call with a person, it's 10 minutes of interaction or whatever it is, probably a bit longer.

In my experience, a lot longer.

And you complete some task in some scheme and you change some database entries around or something like that.

So you keep repeating something over and over again, and that's your job.

So basically, you do want to bring in the task horizon, how long it takes to perform a task.

And then you want to also remove context, like you're not dealing with different parts of services of companies or other customers.