Comment by stevenhuang
3 years ago
There are flaws but also consider PEBCAK error.
For one next time when it starts hallucinating and a gentle course correction doesn't do it, just start a new chat with a different prompt approach. Having the error in its context reinforces the same mistake and sometimes it can't get out of this loop.
PEBKAC in what context? The prompts themselves or the documentation? Because I got Active Collab running on NGINX myself.
I already did this in terms of starting new chats, I spent days on it, and consulted with half a dozen devs supposedly using it in their workflows. It's very easy to make it hallucinate.
In terms of using gpt optimally. But fair enough. If you tried it in multiple sessions trying to convert Apache rewrites to nginx and it wasn't able to do it, I guess this is another failure mode. I just found that curious because chatgpt is usually very very good at regex.
Side note is Google extra terrible lately or is there really no docs on this almost anywhere?
All I could find about it is this and the rules looked very simple, from my experience chatgpt should have got this https://activecollab.com/help/books/self-hosted-activecollab...
That's the documentation on the URL. And yeah, I was surprised too given how people had hyped it so heavily in much more complex scenarios for dev work (well, claimed to anyway, they haven't documented it in most cases of claiming to x).
> but also consider PEBCAK error.
No. It's an AI error, the person between the chair and keyboard just hit enter. If this "error" goes away when I hit the enter key a few more times and get lucky, it's not my fault.
Well, the error doesn't go away, it's a "fail state", but that still doesn't mean PEBCAK either.