Taking credit for something you didn't do, whether it was done by another person or by an LLM, is dishonest and unethical. Prompting an LLM to create something is obviously not the same thing as creating it, and I feel this article is trying to normalize tacit plagiarism. In most contexts I'm aware of where assigning credit actually matters, human authorship and LLM authorship are very much distinguished, and failing…
If I plan a project to build an app and write the full technical specifications and architecture myself, draft data structures, and even provide logic suggestions, and then hand it over to a team of humans to implement - it is at least my teams work. A case can be made that it still primarily my own work (no one expresses much issue with the title: Sid Meier's Civilization as an example). If I have a large amount of…
Don't credit the LLM
31–40 of 51 posts
Re: Don't credit the LLM
#32An LLM is not me. It is capable of doing more "work" but it also doesn't have my mental models and experience. My colleagues know roughly my areas of expertise. If I say "I think that X is happening" they'll assume that is the result of my expertise being applied and react accordingly. If I say "[LLM] thinks X is happening" they'll react differently and I want them to . Just like I might say "I suspect X is happening…
it didn't. it produced an output, and you hopefully invoked some human judgement before believing it was worth sharing, and you are hopefully expecting to be accountable if that judgement was incorrect (whatever the failure mode)
Re: Don't credit the LLM
#33An LLM is not me. It is capable of doing more "work" but it also doesn't have my mental models and experience. My colleagues know roughly my areas of expertise. If I say "I think that X is happening" they'll assume that is the result of my expertise being applied and react accordingly. If I say "[LLM] thinks X is happening" they'll react differently and I want them to . Just like I might say "I suspect X is happening…
the phrase "[LLM] thinks X is happening" is good chunk of the problem it didn't. it produced an output, and you hopefully invoked some human judgement before believing it was worth sharing, and you are hopefully expecting to be accountable if that judgement was incorrect (whatever the failure mode)
Re: Don't credit the LLM
#34I did in fact "bother to review" the tests, and I thought they were good enough to merge. Indeed, they were better than what I would have written on my own: they were lower-quality on a line-by-line basis, but for tests, quantity is a quality of its own, and I would not have bothered to write nearly as many tests. Even so, it was worth flagging that Claude wrote them.
If I trusted LLMs more, would I still feel the need to credit them? Maybe. They are improving very quickly, and I think they will eventually improve to the point where a mostly-LLM-written PR will be as good as mine in every way. Then it will no longer be necessary to apologize for submitting LLM code. But if and when that point is reached, I wouldn’t get used to taking credit for said code! Because it probably won’t be much longer until the human in the loop becomes redundant.
Going back to today, I don’t feel the need to credit LLMs when I use them for tasks that don’t involve submitting their output. In particular, they have recently become quite good at finding bugs in my code.
Re: Don't credit the LLM
#35Re: Don't credit the LLM
#36By not crediting and personifying the LLM, one (re)takes full human responsibility over the produced works and stated claims. As a result one won’t become an “agent” for the LLM.
The title could have been Don’t blame the LLM.
When we first started using LLMs professionally it was fine to hide behind disclaimers. Now with widespread adoption it’s time to step out of the LLM’s shadow and take credit/blame again.
Re: Don't credit the LLM
#37So many comments in here are missing the point. By not crediting and personifying the LLM, one (re)takes full human responsibility over the produced works and stated claims. As a result one won’t become an “agent” for the LLM. The title could have been Don’t blame the LLM. When we first started using LLMs professionally it was fine to hide behind disclaimers. Now with widespread adoption it’s time to step out of the…
Unfortunately, it conflates what's meant by co-authoring. Because so far, Claude has not claimed sovereignty as an artificial intelligence, so actually, mentally crediting Claude is like crediting Vim or Emacs.
We don't have to think of our tools as being authors just because Anthropic did.
The Co-authored-by had a real meaning related to accountability.
Putting our tool in front of us is like letting our cat drive the car. I mean, it's fine if it sits in our lap with the paws on the wheel wearing sunglasses. Just don't pretend it is the one deciding the direction, taking critical turns. Because when we get pulled over, the cops aren't gonna buy it. And neither is anyone on GitHub. We know Claude is still just a program.
Re: Don't credit the LLM
#38So many comments in here are missing the point. By not crediting and personifying the LLM, one (re)takes full human responsibility over the produced works and stated claims. As a result one won’t become an “agent” for the LLM. The title could have been Don’t blame the LLM. When we first started using LLMs professionally it was fine to hide behind disclaimers. Now with widespread adoption it’s time to step out of the…
Re: Don't credit the LLM
#39Earlier quoted context omitted.
If I plan a project to build an app and write the full technical specifications and architecture myself, draft data structures, and even provide logic suggestions, and then hand it over to a team of humans to implement - it is at least my teams work. A case can be made that it still primarily my own work (no one expresses much issue with the title: Sid Meier's Civilization as an example). If I have a large amount of…
I don't understand this rebuttal at all. There is a huge difference between having an idea and implementing it yourself, and handing your idea (plus suggestions and data structures or whatever) to other people to implement. In the latter case, the team completing the project gets a lot of credit for the work. That has certainly been the case everywhere I've worked, and I wouldn't have it any other way, even in cases…