Post #3445178
2026-06-26 18:43 UTC
I’m sorry but “refusing LLM contributions” is stupid. Let me explain though what I mean because it’s not quite what you think it is.
LLMS do not contribute. The image I’m taking recently to explain that to people is that LLMs are like state of the art medical equipment. If it’s made available to you and someone is bleeding to death in front of you, you won’t know what to do with it and the person will die. But chances are that if you’re a trained surgeon on they won’t.
LLMs are but a tool. They amplify your qualities and your defects. An excellent engineer will know how to review LLM production and will have code that is meaningfully good. The problem is mediocre people who would not have been able to produce anything on their own and that produce -something- with an LLM and can’t really assess its quality because they lacked the skills in the first place.
LLMS are really great tools when you use them well. Provided with proper context, frontier models are vastly better reviewers than I am for example. They catch all the silly stuff I lack attention for on a large review and that allows me to focus on the really difficult and subtle stuff. Should you refuse LLms reviewed code? Of course not that would be insanity.
Anyway. Any time I see a new project that has blanket statements about “refusing LLM contributions” a part of me is sad. Those are ideological non practical positions.
Replies (1)
-
@tihmstar@infosec.exchange 2026-06-28 09:07
@madcoder@infosec.exchange My opinion on this is: it's about who takes responsibility, blame for the code written. If you see "LLM wrote this" then whoever prompted the LLM isn't gonna take any blame for when the code is shit (only take credit when it's good). If it's shit it'll be like "go figure that out with the LLM. it probably just halucinated i'm not at fault". If a human takes responsibility (blame) for code i don't care if he used LLM or not. If it's good ok, if it's shit i'm never trusting him again