They can be useful for exploration and learning, sure. But lots of people are literally just copy-pasting code from LLMs - They just do it via an “accept copilot suggestion” button instead of actual copy paste.
Sure, people use all sorts of tools badly, that’s a problem with the user not the tool (generally, I would accept poor tool design can be a factor).
I really dislike the statement of “LLMs dont know anything they are just statistical models” it’s such a thought terminating cliche that is either vacuous or wrong depending on which way you mean it. If you mean they have no information content that’s just factually wrong, clearly they do. If you mean they dont understand concepts in the same way as a person does, well yes but neither does google search and we have no problem using that as the start point of finding out about things. If you mean they can get answers wrong, its not like people are infallible either (who I assume you agree do know things).
You can dislike the statement all you want, but they literally do not have a way to know things. They provide a convincing illusion of knowledge through statistical likelihood of the next token occurring, but they have no internal mechanism for looking up information.
They have no fact repositories to rely on.
They do not possess the ability to know what is and is not correct.
They cannot check documentation or verify that a function or library or API endpoint exists, even though they will confidently create calls to them.
They are statistical models, calculating how likely the next token is based on transformations in a many-dimensional space in which the relationships between existing tokens are treated as vectors in a process for determining the next token.
They have their uses, but relying on them for factual information (which includes knowledge of apis and libraries) is a bad idea. They are just as likely to provide realistic answers as they are to make up fake answers and present them as real.
They are good for inspiration or a jumping off point, but should always be fact checked and validated.
They’re fantastic at transforming data from one format to another, or extracting data from natural language written information. I’m even using one in a project to guess at filling in a form based on an incoming customer email.
They do not possess the ability to know what is and is not correct.
They cannot check documentation or verify that a function or library or API endpoint exists, even though they will confidently create calls to them.
These three are all just the same as asking a person about them, they might know or might not but they cant right there and then check. Yes LLMs due to their nature cannot access a region marked “C# methods” or whatever, but large models do have some of that information embedded in them, if they didnt they wouldnt get correct answers anywhere near as often as they do, which for large models and common languages/frameworks is most of the time. This is before getting into retrieval augmented generation where they do have access to repositories of fact.
This is what I was complaining about in the original post I replied to, no-where have I or anyone else I’ve seen in this thread say you should rely on these models, just that they are a useful input. Yet relying on them and using them without verification is the position you and the other poster are arguing against.
Sure, people use all sorts of tools badly, that’s a problem with the user not the tool (generally, I would accept poor tool design can be a factor).
I really dislike the statement of “LLMs dont know anything they are just statistical models” it’s such a thought terminating cliche that is either vacuous or wrong depending on which way you mean it. If you mean they have no information content that’s just factually wrong, clearly they do. If you mean they dont understand concepts in the same way as a person does, well yes but neither does google search and we have no problem using that as the start point of finding out about things. If you mean they can get answers wrong, its not like people are infallible either (who I assume you agree do know things).
You can dislike the statement all you want, but they literally do not have a way to know things. They provide a convincing illusion of knowledge through statistical likelihood of the next token occurring, but they have no internal mechanism for looking up information.
They have no fact repositories to rely on.
They do not possess the ability to know what is and is not correct.
They cannot check documentation or verify that a function or library or API endpoint exists, even though they will confidently create calls to them.
They are statistical models, calculating how likely the next token is based on transformations in a many-dimensional space in which the relationships between existing tokens are treated as vectors in a process for determining the next token.
They have their uses, but relying on them for factual information (which includes knowledge of apis and libraries) is a bad idea. They are just as likely to provide realistic answers as they are to make up fake answers and present them as real.
They are good for inspiration or a jumping off point, but should always be fact checked and validated.
They’re fantastic at transforming data from one format to another, or extracting data from natural language written information. I’m even using one in a project to guess at filling in a form based on an incoming customer email.
These three are all just the same as asking a person about them, they might know or might not but they cant right there and then check. Yes LLMs due to their nature cannot access a region marked “C# methods” or whatever, but large models do have some of that information embedded in them, if they didnt they wouldnt get correct answers anywhere near as often as they do, which for large models and common languages/frameworks is most of the time. This is before getting into retrieval augmented generation where they do have access to repositories of fact.
This is what I was complaining about in the original post I replied to, no-where have I or anyone else I’ve seen in this thread say you should rely on these models, just that they are a useful input. Yet relying on them and using them without verification is the position you and the other poster are arguing against.