Reading this article posted by @bagder made me realize that I haven't seen ANYBODY explaining exactly what the long-term strategy vis-a-vis code maintenance is, when the code itself was "written" by a junior using ChatGPT. The junior is definitely not going to be able to help (since they're not going to learn and become a senior), so is the expectation that somebody else will use ChatGPT again to update it to use newer libraries etc? Sounds... silly.
construct.net/en/blogs/ashleys…
The reality of long-term software maintenance from the maintainer's perspective
I was reading about a dispute involving the Linux kernel recently (which for the record I don't think either side handled well), and I realised something: Very...Construct


daniel:// stenberg://
in reply to pgcd • • •I don't think it matters who or what wrote the code. Once a maintainer accepts the code, its their code. Then its the maintainers job. We just need to try to make sure the code is as good as possible before we accept it.
un.curl.dev/code/youownit.html
Once merged, you own it - Uncurled
un.curl.devpgcd
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to pgcd • • •