Flutterby™! : Code completion gets it wrong

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Code completion gets it wrong

2025-07-29 17:17:14.6007+02 by Dan Lyke 1 comments

Ars Technica: Two major AI coding tools wiped out user data after making cascading mistakes — "I have failed you completely and catastrophically," wrote Gemini.. I was gonna get completely up in arms over that anthorpomorphization, but the author gets it:

It's worth noting that AI models cannot assess their own capabilities. This is because they lack introspection into their training, surrounding system architecture, or performance boundaries. They often provide responses about what they can or cannot do as confabulations based on training patterns rather than genuine self-knowledge, leading to situations where they confidently claim impossibility for tasks they can actually perform—or conversely, claim competence in areas where they fail.

If there are positive things that come out of the mass delusion that is AI, backups and version control are gonna be two of them...

[ related topics: Interactive Drama Software Engineering Theater & Plays Artificial Intelligence Architecture ]

comments in ascending chronological order (reverse):

#Comment Re: Code completion gets it wrong made: 2025-07-29 21:50:15.076844+02 by: spc476

Version control will not help if one is doing pure vibe coding (not caring about the code, etc.). Do you check in the C sludge that lex outputs, or the lex code itself? If you are pure vibe coding, the prompts are the source code, not the generated code.

AI bros can be irrational longer than you can remain sane …

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.