4 ms·
I like it for condensing long stack traces and very very simple requests, but it really falters when you try to do anything domain specific. Library documentat
by huimang 3y ago
I like it for condensing long stack traces and very very simple requests, but it really falters when you try to do anything domain specific.
Library documentation? Yeah, it doesn't really save time when GPT makes up functions and libraries, making me check the docs anyways...
I was initially hopeful but I find it gets in my way for anything not trivial.
- mypalmike 3y agoI find it to be hit or miss in this aspect. Sometimes I can write a comment about how I want to use an API that I don't know well, and it generates perfect, idiomatic code to do exactly what I want. I quickly wrote a couple of Mastodon bots in golang, leaning heavily on Copilot due to my lack of familiarity with both the language and Mastodon APIs. But yes, sonetimes it just spits out imaginary garbage. Overall it's a win for my productivity - the failures are fast and obvious and just result in my doing things the old way.
- CamperBob2 3y agoYeah, it doesn't really save time when GPT makes up functions and libraries, making me check the docs anyways... That behavior is now vanishingly-rare, at least in GPT4.
- dukeyukey 3y agoSo Copilot uses GPT-4 under the hood, and about half the time I use it to generate anything bigger than a couple of lines it doesn't even compile, let alone be correct. It hallucinates constantly.