> This makes a lot of sense to me. It relates to an idea I've seen circulating elsewhere: if a PR was mostly written by an LLM, why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem?
You may as well say "if someone else can do it I'll just do it myself". It takes skill and taste to know what to ask, wisdom to recognize mistakes, and time and money to fix them.
This is true, but who do you think knows better what to ask, or has better taste with regards to the open source project? The maintainer? Or the guy shooting a drive by LLM PR? I agree though that it still takes time and effort to make good code contributions with LLMs, but probably less time for the maintainer to do it than for a maintainer to review lots of bad LLM PRs to get the good ones.
You may as well say "if someone else can do it I'll just do it myself". It takes skill and taste to know what to ask, wisdom to recognize mistakes, and time and money to fix them.