Generative AI Will Not Kill Developer Jobs
Large language models have taken the world by storm. By now, it’s pretty clear that they are capable of more than originally expected, both by the public as well as their creators. Software developers in particular have been surprised by how good LLM-based tools are at writing code, and even entire applications. With this success of AI comes the argument that it will kill jobs. Like cars and computers did in their day, it raises the ghost of the fear of growing unemployment. For previous technology innovations, that didn’t happen. Is this time different?
It’s not. AI will not kill jobs for software developers. In fact, my prediction is that AI will create more jobs for them than it kills. Those engaging in the fear-mongering misunderstand the fundamental goal of a software developer. Yes, they write code. But code itself is not the final output of a software developer. The goal is solving a problem for a user. And while the current AI tools are good at writing code, they can’t yet solve the problem independently. That may change soon. But this change requires another breakthrough comparable to the creation of LLMs. Today’s AI models don’t have agency. Moving to agent-like systems requires solving many difficult problems in AI - a fact acknowledged by many of the experts in the area (e.g. see this interview with Demis Hassabis).
Even if we create AI which can independently solve a problem for a user, someone still needs to direct that AI. Software developers are ideally placed to do this. Having experience in pre-AI technology puts you in a unique position to understand the mistakes it would make, and correct them. One of the reasons for my mindblowing experience with Cursor was that I was able to debug and fix problems, not just write code. But that still requires a human behind the wheel who knows what to ask, how to write a prompt for the AI and think critically about the offered solution. Solving a problem through software is still an iterative process. It requires adaptive learning in a complex domain. It sometimes requires trial and error to discover solutions. Humans are still best at these activities.
Lastly, I’m sure LLMs will become better with time. Maybe some day they will be able to do everything a software developer does today. That still doesn’t mean the job of a developer would disappear. The car didn’t kill the job of a driver, but changed it. It required different skills. The computer didn’t kill the job of an accountant or banker. It made accountants and bankers more efficient. You could say these jobs kept their names but are fundamentally different, and you would be right. Accountants don’t spend their time doing manual calculations any more. They focus on the strategy of accounting. Is that the same job? In outcomes for the user, yes. In what you do day to day - most definitely not.
It doesn’t matter though, because that’s always how technological progress works. It changes how humans have to behave, sometimes fundamentally. The important thing is that we’re all better off as a result. We are better off not only through being more efficient, but also through opportunities which didn’t exist before. Yes, the car made drivers more efficient. But it also enabled suburbs, larger cities, and practically served as the first product for the assemly line, which has had immeasurable value for everyone. And I’ll leave it as an exercise for the reader to measure the value of the opportunity created by computers.
Developer jobs are safe; in fact GenAI may be a big boon for them. The caveat is that to benefit, you need to be open-minded. I like how someone at work recently summarised this: “AI will not take your job. But someone using it might.”