Live data from Hacker News

MDN can now automatically lie to people seeking technical information

github.com

71–80 of 83 posts

Re: MDN can now automatically lie to people seeking technical information

#71
post #69

Earlier quoted context omitted.

I was thinking more about SSRI's, which make up over half ( https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8450889/ ) of US pharmacy orders. While we do know that they work for some people, they only work for 20% of people ( https://www.ncbi.nlm.nih.gov/books/NBK361016/ ). They also come with common side effects that can lower quality of life ( https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2719451/ ). And we do not unde…

Your own links demonstrate the fundamental difference. The side effects have been studied and can be identified. I'm at this very moment taking a break from a medication because I was able to recognize a severe side effect that came up. I can't recognize when an LLM has generated a nonsensical piece of technical documentation; if I could, I wouldn't need to use it in the first place.

The side effects of incompatible code are similar to the side effects of incompatible medication. Thanks to the identified undesirable effects, you usually identify the problem and resolve the issue with other resources. Occasionally the problem is more severe or persists unidentified. We should definitely be working to minimize these effects and prevent them where possible, but that doesn’t mean we stop trying/utilizing medicine. These are honestly just all the same arguments used against Wikipedia.

Re: MDN can now automatically lie to people seeking technical information

#73
post #71

Earlier quoted context omitted.

Your own links demonstrate the fundamental difference. The side effects have been studied and can be identified. I'm at this very moment taking a break from a medication because I was able to recognize a severe side effect that came up. I can't recognize when an LLM has generated a nonsensical piece of technical documentation; if I could, I wouldn't need to use it in the first place.

The side effects of incompatible code are similar to the side effects of incompatible medication. Thanks to the identified undesirable effects, you usually identify the problem and resolve the issue with other resources. Occasionally the problem is more severe or persists unidentified. We should definitely be working to minimize these effects and prevent them where possible, but that doesn’t mean we stop trying/utili…

- “Incompatible code”? What does this even mean? “Incompatible” with what?

- Have you actually read the examples in the linked github issue? What “undesirable effect” are you able to identify when an LLM tells you that a JS function simply doesn’t exist? Or when something fails subtly enough that the code you wrote based on the LLM’s advice isn’t the obvious culprit? Do you do much debugging?

- Wikipedia requires references, while this LLM directly contradicts the one data source that it’s meant to help explain. Failing to see the comparison.

Re: MDN can now automatically lie to people seeking technical information

#74
post #71

Earlier quoted context omitted.

The side effects of incompatible code are similar to the side effects of incompatible medication. Thanks to the identified undesirable effects, you usually identify the problem and resolve the issue with other resources. Occasionally the problem is more severe or persists unidentified. We should definitely be working to minimize these effects and prevent them where possible, but that doesn’t mean we stop trying/utili…

- “Incompatible code”? What does this even mean? “Incompatible” with what? - Have you actually read the examples in the linked github issue? What “undesirable effect” are you able to identify when an LLM tells you that a JS function simply doesn’t exist? Or when something fails subtly enough that the code you wrote based on the LLM’s advice isn’t the obvious culprit? Do you do much debugging? - Wikipedia requires ref…

If a medication is incompatible with a person's specific biology, they don’t see improvement (or their health declines). If a function is described incorrectly, you won’t see improved functionality (or you’ll see bugs). It was incompatible with the syntax/compiler/the rest of the code.

Though this one won't, LLMs will cite references if asked. They’ll also provide step-by-step rationalization (though they don’t think in that way). Just like Wikipedia, you still have to check those references to verify.

Re: MDN can now automatically lie to people seeking technical information

#75
post #74

Earlier quoted context omitted.

- “Incompatible code”? What does this even mean? “Incompatible” with what? - Have you actually read the examples in the linked github issue? What “undesirable effect” are you able to identify when an LLM tells you that a JS function simply doesn’t exist? Or when something fails subtly enough that the code you wrote based on the LLM’s advice isn’t the obvious culprit? Do you do much debugging? - Wikipedia requires ref…

If a medication is incompatible with a person's specific biology, they don’t see improvement (or their health declines). If a function is described incorrectly, you won’t see improved functionality (or you’ll see bugs). It was incompatible with the syntax/compiler/the rest of the code. Though this one won't, LLMs will cite references if asked. They’ll also provide step-by-step rationalization (though they don’t think…

> If a medication is incompatible with a person's specific biology, they don’t see improvement (or their health declines).

And the specific ways that their health might decline have been studied, a list of which is included with every package of the medicine. Maybe you even get regular bloodwork to check for the specific side effects this medicine’s been seen to cause.

> If a function is described incorrectly, you won’t see improved functionality (or you’ll see bugs).

Hopefully! Again, how much development/debugging do you do on a daily basis? Because real developers don't accept the notion that it's ok for bugs to occur as a result of following reference documentation.

Re: MDN can now automatically lie to people seeking technical information

#76
post #25

I actually think this feature would be fine if implemented better. GPT-4 is perfectly capable of accurately explaining what a short code block does if you prompt it with relevant documentation… which MDN has in abundance, but isn’t using, for some reason. The mistakes seem to be (1) using GPT 3.5 instead because it’s cost effective, even though GPT 3.5 has severe issues with hallucination, and (2) not including conte…

Does GPT-4 really never hallucinate? This is the first time I've personally heard someone claiming anything like that, though I don't tend to do anything with LLMs (due to this bullshit factor).

Anyone who says that GPT-4 doesn't hallucinate is either clueless or an AI grifter, though I don't think GP was claiming that, just calling out that GPT-3.5 is really, really bad at it.

Re: MDN can now automatically lie to people seeking technical information

#77
post #74

Earlier quoted context omitted.

If a medication is incompatible with a person's specific biology, they don’t see improvement (or their health declines). If a function is described incorrectly, you won’t see improved functionality (or you’ll see bugs). It was incompatible with the syntax/compiler/the rest of the code. Though this one won't, LLMs will cite references if asked. They’ll also provide step-by-step rationalization (though they don’t think…

> If a medication is incompatible with a person's specific biology, they don’t see improvement (or their health declines). And the specific ways that their health might decline have been studied, a list of which is included with every package of the medicine. Maybe you even get regular bloodwork to check for the specific side effects this medicine’s been seen to cause. > If a function is described incorrectly, you wo…

[deleted]

Re: MDN can now automatically lie to people seeking technical information

#78
post #36

@dang: Title is clickbait. Perhaps replace with something like: Bug report: MDN's AI Explain feature generates false explanations

The HN guidelines are to use the title of the source article, which this does - and in this case it seems pretty accurate.

> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.

-- https://news.ycombinator.com/newsguidelines.html

Re: MDN can now automatically lie to people seeking technical information

#79

Earlier quoted context omitted.

Does GPT-4 really never hallucinate? This is the first time I've personally heard someone claiming anything like that, though I don't tend to do anything with LLMs (due to this bullshit factor).

Anyone who says that GPT-4 doesn't hallucinate is either clueless or an AI grifter, though I don't think GP was claiming that, just calling out that GPT-3.5 is really, really bad at it.

Cool, thanks for clarifying. Was hoping they'd managed to crack that nut, but doesn't seem like it yet. :)

Re: MDN can now automatically lie to people seeking technical information

#80

Hey ChatGPT, please generate a Firefox Corp-style apology for this snafu... Be sure to use some bullshit blah blah for our original aim of wanting to enhance user experience and listening to the users' feedback, and some more bullshit blah blah about doing better in the future.

ChatGPT: I apologize for any inconvenience caused by the recent addition of the "ai assistant" feature on the MDN website. We understand that this feature has generated misleading information, leading to confusion and frustration among users. As an AI model, I acknowledge that the generated text may contain convincing falsehoods or inaccuracies.

At Mozilla, our goal has always been to provide accurate and reliable technical information to the developer community. Unfortunately, in this instance, the introduction of the AI feature did not align with that objective. We deeply regret the impact it has had on users seeking reliable information.

Our intention with the AI assistant was to enhance the user experience by providing additional context and explanations. We wanted to create a trusted companion that would assist developers in understanding complex concepts more easily. However, we recognize that this implementation fell short of expectations and introduced more problems than solutions.

We value the feedback and concerns raised by the community, and we take them seriously. Going forward, we will reassess our approach to ensure that any new features or enhancements undergo thorough review and testing. We will prioritize human oversight, peer-review, and fact-checking to ensure the accuracy and reliability of the information presented on MDN.

Our commitment to providing a reliable resource for developers remains unwavering, and we apologize for any loss of trust this incident may have caused. We appreciate your patience as we work to rectify the situation and improve the overall user experience on MDN.

Thank you for your continued support, and we assure you that we will learn from this mistake and strive to do better in the future.

Sincerely, [Your Name] Mozilla Community Manager

https://chat.openai.com/share/2649a208-7987-4c30-9bed-0738b8...

Post reply on HN