Not many people realize that the job of an AI engineer is *not* about training AIs. It used to be, yes. Just like once upon a time the job of an AI engineer was about coding heuristic rules, and before that it was just plain logic programming.
We have for some years now switched from curating training data and training #AIs on those to designing continuous processes and systems which allow the AIs to train themselves.
There are many ways to do this:
- Design families of games where AIs can compete against each others. The age of single games has been over for a while now, now it's about making AIs create masses of games each with novel rules and play those.
- Make AIs themselves curate training data from suitable sources.
- Make AIs refine the training data by evaluating it continuously, or by simply making progressive improvement steps on it.
- Make AIs perform easier inverse tasks, and then turn those around into harder tasks.
- Make AIs self-improve both in designing new kinds of tasks for example in domains like mathematics and software engineering, and also in the tasks themselves and in evaluating the quality of the solutions.
In a way, the AIs are pulling themselves out from unreality into the material world, and we're just supporting them in that.