←back to thread

628 points cratermoon | 1 comments | | HN request time: 0.334s | source
Show context
tptacek ◴[] No.44461381[source]
LLM output is crap. It’s just crap. It sucks, and is bad.

Still don't get it. LLM outputs are nondeterministic. LLMs invent APIs that don't exist. That's why you filter those outputs through agent constructions, which actually compile code. The nondeterminism of LLMs don't make your compiler nondeterministic.

All sorts of ways to knock LLM-generated code. Most I disagree with, all colorable. But this article is based on a model of LLM code generation from 6 months ago which is simply no longer true, and you can't gaslight your way back to Q1 2024.

replies(7): >>44461418 #>>44461426 #>>44461474 #>>44461544 #>>44461933 #>>44461994 #>>44463037 #
62702b077f3 ◴[] No.44461426[source]
> The garbage generator generates garbage, but if you run it enough times it gets something slightly-less-garbage that can satisfy a compiler! You're stupid if you don't think this is awesome!
replies(4): >>44461513 #>>44461517 #>>44461643 #>>44462226 #
KPGv2 ◴[] No.44461513[source]
I had Copilot for a hot minute. When I wrote things like serializers and deserializers, it was incredible. So much time saved. But I didn't do it enough to make the personal cost worth it, so I cancelled.

It's annoying to have to hand-code that stuff. But without Copilot I have to. Or I can write some arcane regex and run it on existing code to get 90% of the way there. But writing the regex also takes a while.

Copilot was literally just suggesting the whole deserialization function after I"d finished the serializer, 100% correct code.

replies(1): >>44462291 #
1. Shorel ◴[] No.44462291[source]
I remember writing LISP code that created the serialisers and deserialisers for me.

Now that everything is containerised and managed by docker style environments, I am thinking about giving SBCL another try, the end users only need to access the same JSON REST APIs anyway.

Everything old is new again =)