3 ms·
You can't read API calls and know if they're real, or if the function names are plausible but non existent. This is the problem with GPT. It creates great sound
by Thorentis 4y ago
You can't read API calls and know if they're real, or if the function names are plausible but non existent. This is the problem with GPT. It creates great sounding possible APIs, but has no idea which APIs actually exist.
- simonw 4y agoThat's the great thing about using GPT for code - unlike factual knowledge, it's very easy to confirm if the code it wrote had errors or not: you run it. The you test it manually with a few more inputs, then you write some automated tests for it (maybe with GPT's assistance).
- politician 4y agoYou can put AI in an iteration loop with a compiler and have it bake a functional test suite overnight. It’s a TDD practitioner’s dream.
- withinboredom 4y agoOh. Now that is pretty slick
- macintux 4y ago“Ran this with no errors, works great” is how you end up with Microsoft exposing everyone’s personal email via Bing.
- IanCal 4y ago> You can't read API calls and know if they're real, or if the function names are plausible but non existent Why not? And if I miss them, my editor, compiler or general testing should pick that up.
- satvikpendem 4y agoYeah, I think many people are using them for dynamically typed languages like Python or Ruby, not Rust or TypeScript. If it's the latter, your compiler will automatically find the errors for you.
- satvikpendem 4y agoIf you use a dynamically typed language like Python or Ruby, sure. I use it for Rust and the compiler immediately catches any errors. Just one more reason I don't use dynamically typed languages.