Ah yes the typical workflow for LLM generated changes:
LLM produces nonsense at the behest of employee A.
Employee B leaves a bunch of edits and suggestions to hammer it into something that’s sloppy but almost kind of makes sense. A soul-sucking error prone process that takes twice as long as just writing the dang code.
Code submitted!
Employee A gets promoted.
Also the fact that this isn’t integrated with tests shows how rushed the implementation was. Not even LLM optimists should want code changes that don’t compile or that break tests.
I just looked at the first PR out of curiosity, and wow…
this isn’t integrated with tests
That’s the part that surprised me the most. It failed the existing automation. Even after prompted to fix the failing tests, it proudly added a commit “fixing” it (it still didn’t pass…something that copilot should really be able to check). Then the dev had to step in and say why the test was failing and how to fix the code to make it pass. With this much handholding all of this could have been done much faster and cleaner without any AI involvement at all.
The point is to get open source maintainers to further train their program because they already scraped all our code. I wonder if this will become a larger trend among corporate owned open source projects.
Ah yes the typical workflow for LLM generated changes:
Also the fact that this isn’t integrated with tests shows how rushed the implementation was. Not even LLM optimists should want code changes that don’t compile or that break tests.
I just looked at the first PR out of curiosity, and wow…
That’s the part that surprised me the most. It failed the existing automation. Even after prompted to fix the failing tests, it proudly added a commit “fixing” it (it still didn’t pass…something that copilot should really be able to check). Then the dev had to step in and say why the test was failing and how to fix the code to make it pass. With this much handholding all of this could have been done much faster and cleaner without any AI involvement at all.
The point is to get open source maintainers to further train their program because they already scraped all our code. I wonder if this will become a larger trend among corporate owned open source projects.