Comment by directevolve

Will the modal developer of 2030 be much like a dev today?

Writing software was a craft. You learned to take a problem and turn it into precise, reliable rules in a special syntax.

If AI takes off, we'll see a new field emerging of AI-oriented architecture and project management. The skills will be different.

How do you deploy a massive compute budget effectively to steer software design when agents are writing the code and you're the only one responsible for the entire project because the company fired all the other engineers (or never hired them) to spend the money on AI instead?

Are there ways of factoring a software project that mitigate the problems of AI? For example, since AI has a hard time in high-context, novel situations but can crank out massive volumes of code almost for free, can you afford to spend more time factoring the project into low-context, heavily documented components that the AI can stitch together easily?

How do you get sufficient reliability in the critical components?

How do you manage a software project when no human understands the code base?

How do you insure and mitigate the risks of AI-designed products? Can you use insurance and lower prices if AI-designed software is riskier? Can we quantify and put a dollar value on the risk of AI-designed software compared to human-designed?

What would be the most useful tools for making large AI-generated codebases inspectable?

When I think about these questions, a lot of them sound like things an manager or analyst might do. They don't sound like the "craft of code." Even if 1 developer in 2030 can do the work of 10 today, that doesn't mean the typical dev today is going to turn into that 10x engineer. It might just be a very different skillset.