|
|
|
|
|
by jchw
1106 days ago
|
|
My problem with GPT-4 so far is that it's most impressive at doing things that I don't really need any help with, but when I ask it something that I find genuinely challenging, it's error prone and often generates suboptimal code. Of course, it's an extreme far cry from Markov chains and earlier models, but at the end of the day, I think it's skipping too many steps right now. To be clear, it's still really impressive. Being able to ask an AI assistant to implement e.g. a Fourier transform in Rust and getting an answer that is correct or quite close is pretty damn impressive. That's something that a lot of programmers would struggle with. But, in a lot of other ways, GPT-4 feels very skin deep, and the illusion is pierced when you realize it has just made a bunch of shit up in its impressive-sounding answer. |
|
That's actually what I like about it. It's pretty good at doing routine tasks that I easily could do, but which are boring and/or time-consuming. That frees me up to do more interesting stuff.
One example I've given here before is porting an extension I wrote for the Atom text editor to VS Code. I have no doubt that I could learn to write extensions for VS Code, but using ChatGPT meant that I didn't have to waste hours learning how to do that. I just took the skeleton code generated by ChatGPT, dropped in my pre-existing code, and boom... done. Since learning to write VS Code extensions isn't my primary goal (or a secondary goal, or even a tertiary goal), that was a clear win for me.
I put off switching to VS Code for far too long after Atom was EOLed, just because I didn't want to take the time to learn how to port my extension.