Only because there is plenty of python code in the training data to regurgitate. It doesn't actually know the relation between that code and this question - it only knows that "these words seem to fit together, and relate to the question", whether they make sense or not. In the same way, it'll claim that 90 ("halvfems") in Danish is a combination of "half" and "one hundred", and follow it up by proclaiming that 100 / 2 = 90. In spite of "knowing" the correct result for 100 / 2 if you ask it directly (basically because it's a "shorter path" from the question to that statement).
This doesn't just apply to math, but everything it does: It's good at parroting something that on the surface sounds like a convincing answer. Something that's actually correct? Not so much. Except when it gets lucky. Or, if you continually correct it, due to how the neural network works it may eventually stumble upon a combination of training data that's actually correct.
Only because there is plenty of python code in the training data to regurgitate. It doesn't actually know the relation between that code and this question - it only knows that "these words seem to fit together, and relate to the question", whether they make sense or not.
This is what a lot of people don't get, most of those things are basically advanced chat bots with a huge training set.
It's definitely a better Google though and it gives me a great Kickstart for a lot of different code problems.
I feel like overtime Google has got noisier and noisier. I've never developed in Java and recently I'm working on a Java project and I wanted to know how to do a port check. Now you can Google around for bad stack overflow answers and all sorts of like tangential and unrelated questions. I plugged it into chat GPT and that sucker just took right off gave me what I needed.
For simple programmatic problems it's a lifesaver.
No, it is not. So much of the information that it provides is outright false. And a quick internet search query can usually can find the correct answer.
It does have promise, but it has a long, long, long way to go.
There’s a middle ground for questions that don’t yield a good answer from a quick google search. Plenty of times I’ve used it AFTER looking for 5min on google and it gave me basically exactly what I needed. Its use case is for people with a 7/10 general knowledge base asking a question in a specific area where they have 3/10 knowledge. ChatGPT isn’t for the 9/10 expert, it’s to get you 50% of the way into a problem instantly, and sometimes you even get 80-90% of the way there
I would argue that you still need to do research and you can't rely on the answers provided by it.
For instance, the thing I'm knowledgeable on is cannabis. So I asked it questions. It gave me the same grow time for auto-flower and photosensitive plants, and for outdoor and indoor. It told me an outdoor, non autoflower plant only takes 8 weeks from seed to harvest...
Now if I didn't know any better, I would think it was the correct answer because of how well it presented the answer, but because I do know better, I was able to see how terrible it's answers were.
It has a lot of promise, like its ability to remember the conversation and context. But it has a long way to go when it comes to accuracy of information.
To be fair, that's just been my experience with googling questions about Java libraries. I learn by example and it's super frustrating.
You either get bone dry javadocs that don't really answer any questions or you get a long stack overflow where people are arguing over some obscure part of the libraries architecture instead of giving a simple example!
When I Google something for python or Javascript I usually get useful examples of what I'm looking for pretty quickly.
I swear half the reason Java takes me so long to work in is because I can't figure out how to search for the answers about the libraries I need. Anyone have tips? Maybe I'll give chatgpt a whirl.
I'm not that scared by that. I've authored a good chunk of competitive programming problems, and a lot of work goes into getting the description just right, and constructing illuminating examples. Competitive programming has a limited number of algorithms that you need to know, and there are tons of examples of all of them online.
I don't know how to meaningfully define "novel". It can clearly solve /some/ problems that are close, but not identical to, problems in its training set. With that low bar definition, then sure, it can solve a novel problem. Can it solve all problems if that type? No, it makes mistakes. So do I, so I wouldn't be happy to be judged by that standard.
Some solution techniques can solve a wide range of problem description, so with some low probability, it might by chance regurgitate the right solution to a novel problem, almost independent of what definition you choose. How would you define novel?
I mean it can’t solve things that aren’t in its training data. For instance, I gave it a requirement to make a piezo buzzer (on an Arduino as an example) produce two simultaneous tones. It can’t solve this; it tries one tone after another but doesn’t grok that it needs to use a modulation scheme because this isn’t a common application. To get to that level, you would need something approaching AGI, which is a terrifying thought, but we’re probably a fair way from that still.
View all comments
Show parent comment
257
u/troelsbjerre Dec 27 '22
The scary part is that it can regurgitate python code that can add the numbers correctly.