[sparker72678]

Maybe I'm an abnormal programmer, but writing code is not the bulk of my job. Solving problems is. Once the solution has actually been defined, the code is usually the easy part.

And usually the solution requires taking into consideration the entire context of the system as it exists so far, as well as making good judgement calls about what will be required in the future. Then, communicating the tradeoffs to a team, and helping them make a decision from among our options.

I don't want to crap on an impressive tool, but "imitate a programmer's code, 50-100 lines at a time" is not the same thing as "do the job of a programmer."

[sph]

Indeed, writing code is the minor part of being a senior engineer. It's a "doing" thing, which AI is getting to the point of being decent at, mostly by copying. Your ChatGPT or Github Copilot are still unable to implement an algorithm no one has written before.

And solving problems? Needs "understanding" and in many cases, "lateral thinking", two features that are not possible with contemporary AI systems until AGI is a thing, and that one is still is science fiction. But solving problems is still the main reason people hire me.