Post by @yogthos@lemmy.ml

2026-10-22 13:52 UTC

The question is why it matters in the first place. As long as the person submitting code takes ownership of the code, and there is a review of the code being done the same as before, nothing actually changes. Your whole line of argument is absurd because it’s premised on the idea that we can trust code produced by a human more than code produced by an LLM. And that’s obviously not true because humans make mistakes all the time. So, the focus on how the code was produced is fundamentally misguided. The focus in any successful project is on validation through things like code reviews, specifications, testing, and other well established practices. That’s what responsible teams have always done.

Replies (2)

@nonentity@sh.itjust.works 2026-10-22 14:41

To me, it matters because the use and reliance on LLMs demonstrably erodes cognitive capacity and ability, and submissions tainted by them should be subjected to an elevated level of scrutiny, which can only be facilitated with a consummate element of transparency. That elevated scrutiny could, and probably should, also be applied to non-LLM infected submissions, but doing so wouldn’t negate the labelling of authorship. Good faith proponents of LLM assisted tooling should be in favour of overt transparency and labelling, as it’s a requirement to facilitate future historical analysis of their utility, efficacy, and legitimacy; you know, to build a body of evidence.

Open ##5199887
@ormith@lemmy.world 2026-10-22 16:37

To me it matters because if you got code from someone else, you’d probably want to credit it to them, right? So why shouldn’t LLM output be treated the same?

Open ##5201285