Conversation

Notices

1. Embed this notice
   Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 08-Nov-2025 09:48:14 JST Erin 💽✨
   My timeline is full of people talking about LLMs making hard to detect mistakes and how it's going to ruin KeyPass XC and all I can think is "folks, have you heard about humans? Ooooh boy...."
   
   Yes I did spend 30 minutes staring at some code going insane trying to find a bug only to discover that a LLM had made a 1 character copy and paste error. At first I was mad and then a moment later I started laughing at realising it was exactly the same shape of bug I had made 100 times before.
   
   They're not miracle workers; they're dumb, make mistakes, are not creative, and typically I find their output to be mediocre. They're also not going to ruin your project unless you're asleep at the wheel or being lazy
   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Saturday, 08-Nov-2025 09:48:12 JST ✧✦Catherine✦✧

     in reply to

     @erincandescent they make different types of bugs, which are specifically more difficult to catch in code review, and they incentivize people to submit more code. I think the danger is real

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Saturday, 08-Nov-2025 09:49:10 JST ✧✦Catherine✦✧

     in reply to

     @erincandescent if one actually gave a fuck about code reliability _or_ productivity, one would reimplement PVS-Studio's lints (which catch many copy/paste errors automatically) for $favorite_language_here instead of wasting time on LLM shit

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Sunday, 09-Nov-2025 02:28:08 JST ✧✦Catherine✦✧

     in reply to

     @erincandescent i have made the same argument in the keypassxc repo and achieved consensus; i rest my case