7 ms·
The fruits of using LLMs to code. You'll waste far more time finding what it quietly and subtly wrecked than you would have if you just coded it yourself.
by VCFundedGenYer 1mo ago
The fruits of using LLMs to code.
You'll waste far more time finding what it quietly and subtly wrecked than you would have if you just coded it yourself.
- vegnus 1mo agoYou're not reading it right. The bug was found using a vibecoded fuzzer.
- 12j3afAv 1mo agoI wonder from where Claude stole this fuzzer.
- pjankiewicz 1mo agoOr it used something called an "analogy" which is a valid way to solve new problems.
- criddell 1mo agoThe very first line of the bug report: > This is a bug found with our fuzzer: https://github.com/daedalus/fuzzer/ https://github.com/daedalus/fuzzer/
- LoganDark 1mo agoI think they're talking about the misconception that LLMs can only ever regurgitate their training data verbatim enough to constitute mass copyright violation. And that that's therefore "stealing"
- jaggederest 1mo agoThose sneaky LLMs going 7 years into the past and committing as a human: https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/8eda3c7f91e1a5b3917ef87ea3249968d5a9f263 https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/8eda3c7f91e1a5b...
- wiseowise 1mo agoIt’s obviously Claude 69 with time travel functionality, that’s too dangerous to release to public. They’re working on space-time limiting sandbox to prevent these issues.
- six_seven 1mo agoIts all fun and games until the Claude-who-remains hunts you down
- jaggederest 1mo agoJust remember kids, never immanentize the eschaton.