[phito]

I don't agree, I looked at most of the code the AI wrote in my project, I have a good idea of how it is architectured because I actively planned it. If I have a bug in my orders, I know I have to go to the orders service. Then it's not much harder than reading the code my coworkers write at my daily job.

[nicce]

Parent comment implied that they don’t plan to read the code at all in the long term.

[pizzafeelsright]

At this point in reality do you read assembly or libraries anymore?

Years ago it was Programmer -> Code -> Compile -> Runtime Now today the Programmer is divided into two entities.

Intention/Prompt Engineer -> AI -> Code -> Compile -> Runtime.

We have entered the 'sudo make me a sandwich' world where computers are now doing our bidding via voice and intent. Despite knowing how low level device drivers work I do not care how a file is stored, in what format, or on what medium. I do want it to function with .open and .write which will work as expected with a working instruction set.

Those who can dive deep into software and hardware problems will retain their jobs or find work doing that which AI cannot. The days of requiring an army of six figure polyglots has passed. As for the ability to production or kernel level work is a matter of time.