2026-10-17 01:56 UTC
Replies (4)
-
@voyage0@sh.itjust.works 2026-10-17 02:54
Predicting what a compiler outputs is quiet hard, especially if you enable optimization flags or get near any undefined behavior. But I think you’re right to say that a compiler is more predictable than any LLM. I don’t get the point why you should be unable to audit the output of an LLM? If its used as a tool like described the user should have the knowlage to audit any output
-
@yogthos@lemmy.ml 2026-10-17 03:16
all the undefined behaviors would like to disagree with you there champ
-
@Ephera@lemmy.ml 2026-10-17 04:35
He is saying that you have to understand your contribution, so whatever the LLM spits out, you need to thoroughly review and double-check that it makes sense. So, in particular, he’s not trying to rate these tools, he’s merely saying make sure the contribution is objectively good, then he doesn’t care how you got there.
-
@sonalder@lemmy.ml 2026-10-17 07:08
You cannot, that’s why reproducible builds are hard. Modern compiler are made with compilers (egg/chicken problem) not assembly nor machine code and you always loose some perfect prediction. Yes LLMs are less predictible than compiler but their output is readable to human, while machine code is very hard (yet not impossible). Is that a bad things that 99% of devs have forgot how to write code cutting holes in paper? Tools are changing and while a direct comparison between the move from paper to COBOL or assembly to C is not the same as python to LLM generated it’s hard to deny that LLM will change how human write code.