I see them sort of like tractors. They'll replace a lot of work, but not all of it. Farmers still have to be tough and strong. Farmers are getting paid a hell l

I see them sort of like tractors. They'll replace a lot of work, but not all of it. Farmers still have to be tough and strong. Farmers are getting paid a hell lot better than they used to in the past, but we still need millions of farmers. The programmers of the future will look more like directors or managers today. Just like a director tries to bring out the best from a skilled actor, an AI-integrated dev needs to properly understand the nuances of the AI they're working with. They don't need to know ML, but they do need to understand the differences in personality between, say, GPT-3 and GPT-J. The other skill would be communication. Newbies talk to AI like they're talking to some kind of oracle. They assume the AI understands without context. A common mistake is something like assuming the AI understands sarcasm without knowing that it's from a source that would be sarcastic. I've often said that you have to talk to it like you'd talk to a child. Teachers often put a lot of effort into explaining things better. You can ask it to write generic "email validation code" easily. What's harder is questions like "build it to this architecture" or "this code is doing X, make it do Y instead". You tell it the steps to reproduce the bug, the conditions that make the bug happen, the expected results and the actual results. So it's still the same skillset used today but you can't get away with being a "good dev who can't work with others" anymore.