In other words, English (or your human language of choice.)
The example is outputting (afaict, skimmed most of it) effectively 15 lines of code. In terms of features, the equivalent of a single button on an ops dashboard page.
That's just not maintainable. Sure, you can write one-off, throwaway "code" this way but there's no way you could build (and maintain) a business this way, at least imo.
You'd need to "regenerate" chunks of your business logic from changed requirements, hoping they'd remain about the same. Thus why I think you'd converge on Math or Legal Code, precise and hopefully reproducible output when slightly tweaked.
It's like running early C++ code through cfront to generate a C program that is then compiled and executed as usual. Except this time, the input is not C++, it's plain English. That is not a small distinction!
For one thing, any reasonably-literate person can now get the computer to do what they want. The specification is now the program itself, a longstanding holy grail of programming. Decades of marketing hype and empty promises of "5GL" languages are now within reach.
As for maintenance, the document that is 'maintained' is the English, not the Python. When the requirements change, regenerate the output. Ideally no human ever needs to see the Python code, much less edit it. (Notice that ChatGPT isn't just generating the code from scratch, but successfully editing it.)
There is no reason to think that small random variations in the exact output code will be a showstopper. Automated test generation will be a big part of the picture, of course.
