←back to thread

Using LLMs at Oxide

(rfd.shared.oxide.computer)
694 points steveklabnik | 3 comments | | HN request time: 0s | source
Show context
csb6 ◴[] No.46179547[source]
Strange to see no mention of potential copyright violations found in LLM-generated code (e.g. LLMs reproducing code from Github verbatim without respecting the license). I would think that would be a pretty important consideration for any software development company, especially one that produces so much free software.
replies(4): >>46179678 #>>46179797 #>>46179941 #>>46188231 #
dboreham ◴[] No.46179678[source]
Is there current generation LLMs do this? I suppose I mean "do this any more than human developers do".
replies(1): >>46180015 #
theresistor ◴[] No.46180015[source]
A very recent example: https://github.com/ocaml/ocaml/pull/14369
replies(2): >>46180102 #>>46180413 #
phyzome ◴[] No.46180102[source]
...what a remarkable thread.
replies(1): >>46180509 #
menaerus ◴[] No.46180509[source]
Right? If this is really true, that some random folk without compiler engineering experience, implemented a completely new feature in ocaml compiler by prompting the LLM to produce the code for him, then I think it really is remarkable.
replies(2): >>46181474 #>>46182364 #
1. ccortes ◴[] No.46181474[source]
Oh wow, is that what you got from this?

It seems more like a non experienced guy asked the LLM to implement something and the LLM just output what and experienced guy did before, and it even gave him the credit

replies(2): >>46181940 #>>46182770 #
2. rcxdude ◴[] No.46181940[source]
Copyright notices and signatures in generative AI output are generally a result of the expectation created by the training data that such things exist, and are generally unrelated to how much the output corresponds to any particular piece of training data, and especially to who exactly produced that work.

(It is, of course, exceptionally lazy to leave such things in if you are using the LLM to assist you with a task, and can cause problems of false attribution. Especially in this case where it seems to have just picked a name of one of the maintainers of the project)

3. menaerus ◴[] No.46182770[source]
Did you take a look at the code? Given your response I figure you did not because if you did you would see that the code was _not_ cloned but genuinely compiled by the LLM.