2026-04-29 06:11 UTC
Replies (4)
-
@danluu@mastodon.social 2026-04-29 06:20
Maybe I should write an updated version of that post for the LLM era? I don't know that it would be more convincing, but I recently tried using a text editor and hit a bug in it, so I tried vibe coding a fuzzer and it took ~6 minutes of my time to find the first bug (text/data corruption). With LLM triage and review of the output, there have been zero false positives so far and I'm getting "my" patches merged. I'm blown away by how easy this is to do now and yet, software quality is declining.
-
@autiomaa@mementomori.social 2026-04-29 06:16
@danluu It might be less about LLMs and more about the quality is thinking and planning of people who build things. Tools and automation can improve speed, but if plans have bigger mistakes, end results often lack a lot.
-
@synlogic4242@social.vivaldi.net 2026-04-29 07:51
@danluu tests & fuzzers good. LLMs bad: unreliable, privacy hole, IP theft actor, legal provenance ambiguity, then its amorality, career risk, dependency increase and de-skilling.
-
@lightbeaminsight@mastodon.social 2026-04-29 23:51
@danluu I enjoyed the post, even if some references and parts went over my head some. I think I’d really love to see a video recording of you setting up a fuzzer with someone who’s not a convert as it were, going through the process of set up, through to success. Other than that, it might be interesting to have people who you’ve helped blog about the process and what they’ve ended up doing