If you're not using external libraries that are maintained by other people, how do you handle your code's maintainability in the long-term? Keep asking ChatGPT to fix it when things break?
You maintain the code the same way those other people maintain their code, testing. They aren't doing anything special here, you still have to write tests (well, you can get GPT to write some of them for you). The upside here is you are the one in control of this and you can change and test to your specific needs. You are not relying on external library who has to appeal to a general huge variety of use cases. You also don't have to deal with a lot of external time-wasters, as you're only working internally so you aren't at the whims of whether or not that group can even work on implementing your change. Plus, no more random changes that catch you by surprise when you're reading the change log.
>Keep asking ChatGPT to fix it when things break?
Hah, maybe some day we will get to that point. Until then we still need to know what is happening, however, you might be surprised to find out how infrequently things require that much input seeing as you aren't at the whims of random other parties constantly.
A self contained bundle of software with no external dependencies cannot break, because it has no externally changing parts, that should be obvious.
I suggest code obfuscation and other acts of tribal knowledge hoarding for job security. ;)