3. evaluating whether the end result works as intended.
I have some news for the author about what 80% of a programmer's job consists of already today.
There is also the issue #4, that "idea guy" types frequently gloss over: If things do not work as intended, find out why they don't do so and work out a way to fix the root cause. It's not impossible that an AI can get good at that, but I haven't seen it so far and it definitely doesn't fit into the standard "write down what I want to have, press button, get results" AI workflows.
Generally, I feel this ignores the inherent value that there is in having an actual understanding of a system.
[...]
3. evaluating whether the end result works as intended.
I have some news for the author about what 80% of a programmer's job consists of already today.
There is also the issue #4, that "idea guy" types frequently gloss over: If things do not work as intended, find out why they don't do so and work out a way to fix the root cause. It's not impossible that an AI can get good at that, but I haven't seen it so far and it definitely doesn't fit into the standard "write down what I want to have, press button, get results" AI workflows.
Generally, I feel this ignores the inherent value that there is in having an actual understanding of a system.