No it is not demeaning, that is simply how you interpret it @dill (sorry you feel that way, TBH). I am simple stating a technical software development fact.
The fact is that experienced coders who use the OpenAI API can look at code posted here which ChatGPT has “written” with-regard-to OpenAI API requests and we can easily see that the code is hallucinating nonsense generated by ChatGPT.
How do we know this? Because ChatGPT uses deprecated API endpoints which have long been deprecated. The same goes for OpenAI API params.
In addition, ChatGPT will hallucinate functions, methods, parameters, etc which do not exist because of its cut-off date of mid 2021. So, when a developer is familiar with the API docs and have written a lot of OpenAI API code, they can immediately spot these hallucinations.
These are the facts. Nothing but the facts.
OpenAI says the same thing when their terms and conditions caution everyone about the mid 2021 cut-off date of their models pre-training data. So does all the literature on generative AI.
If you don’t believe me, @dill, read this paper released a few days ago by OpenAI:
It’s best to stick to technical facts @dill and not personality, your own biases and feeling about ChatGPT, and words or how experienced OpenAI API software developers here state a well-known technical fact (and serious limitation) about ChatGPT.
Can you easily spot when ChatGPT “makes up nonsense” when it generates OpenAI API related code, @dill ? Many of us who write OpenAPI API code can spot this kind of “ChatGPT generated spam code” in seconds.
However, we devs here do not yet “flag” ChatGPT generated spam code as such, as we understand many passionate ChatGPT users have not learned the limitations of generative AI (again, please visit link above and read OpenAI’s March 2023 research paper on GPT4).
Thanks.
