Earlier quoted context omitted.
I really hope you're not a software engineer and saying this. But just as a lighting round of issues. 1. code can be correct but non-performant, be it in time or space. A lot of my domain is fixing "correct" code so it's actually of value. 2. code can be correct, but unmaintainable. If you ever need to update that code, you are adding immense tech debt with code you do not understand. 3. code can be correct, but not…
This is a straw man. Consider that from my perspective, each of your points amount to saying "code can be correct, but incorrect" (take a look at number 5) and you may realize that your argument does not make any sense: 1. If code is "correct" but non-performant when it needs to be performant, then it's not correct. 2. If code is "correct" but unmaintainable when it needs to be maintainable, then it's not correct. 3.…
We took you to mean correct as in, given the right inputs, you get the expected outputs. And in that case, our objections do apply. In addition, if correct does mean overall fit-to-purpose the way you are suggesting here, then by gosh my points stands and no code generated by AI is correct! (Because of a variety of factors outside of simply "does the output of this code indicate that it seems to be working")