That's a very constructive way of responding to AI being hot trash.
Well, the OP reviewed the "AI" output, deemed it useful and only then implemented it.
This is generally how you work with LLMs.
Adding a feature because ChatGPT incorrectly thinks it exists
31–40 of 451 posts
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#32I have fun asking Chatbots how to clear the chat and seeing how many refer to non-existent buttons or menu options
I tried asking chat bots about a car problem with a tailgate. They all told me to look for a manual tailgate release. When I responded asking if that model actually had a manual release, they all responded with no, and then some more info suggesting I look for the manual release. None even got close to a useful answer.
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#33"Should we really be developing features in response to misinformation?"
No, because you'll be held responsible for the misinformation being accurate: users will say it is YOUR fault when they learn stuff wrong.
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#34[deleted]
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#35I've come across something related when building the indexing tool for my vintage ad archive using OpenAI vision. No matter how I tried to prompt engineer the entity extraction into the defined structure I was looking for, OpenAI simply has its own ideas. Some of those ideas are actually good! For example it was extracting celebrity names, I hadn't thought of that. For other things, it would simply not follow my instructions. So I decided to just mostly match what it chooses to give me. And I have a secondary mapping on my end to get to the final structure.
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#36I've found this to be one of the most useful ways to use (at least) GPT-4 for programming. Instead of telling it how an API works, I make it guess, maybe starting with some example code to which a feature needs to be added. Sometimes it comes up with a better approach than I had thought of. Then I change the API so that its code works. Conversely, I sometimes present it with some existing code and ask it what it does…
[deleted]
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#37I wrote this the other day: > Hallucinations can sometimes serve the same role as TDD. If an LLM hallucinates a method that doesn’t exist, sometimes that’s because it makes sense to have a method like that and you should implement it. — https://www.threads.com/@jimdabell/post/DLek0rbSmEM I guess it’s true for product features as well.
Seems like lots of us have stumbled on this. It’s not the worst way to dev!
> Maybe hallucinations of vibe coders are just a suggestion those API calls should have existed in the first place.
> Hallucination-driven-development is in.
https://x.com/pwnies/status/1922759748014772488?s=46&t=bwJTI...
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#38Anyone who has worked at a B2B startup with a rouge sales team won't be surprised at all by quickly pivoting the backlog in response to a hallucinated missing feature.
I'm guessing you meant "a sales team that has gone rogue" [1], not "a sales team whose product is rouge" [2]? ;-)
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#39> ChatGPT was outright lying to people. And making us look bad in the process, setting false expectations about our service.
I find it interesting that any user would attribute this issue to Soundslice. As a user, I would be annoyed that GPT is lying and wouldn't think twice about Soundslice looking bad in the process
Re: Adding a feature because ChatGPT incorrectly thinks it exists
#40slightly off topic: but on the topic of AI coding agents making up apis and features that don’t exist, I’ve had good success with Q telling it to “check the sources to make sure the apis actually exist”. sometimes it will even request to read/decompile (java) sources, and do grep and find commands to find out what methods the api actually contains