I can't go back to using it. I spent too much time reviewing the code it spit out and noticed when it absolutely wouldn't do what I needed it to, I was absolute slog since it was some else code.
There seem to be two different camps here: Copilot-users that use it largely for autocomplete and Cursor/Sonnet-users that use it for generating larger blocks of code. Personally I'm in the former camp; the efficiency gains are substantial and hallucinations are easy to control. Larger blocks are fine if one wants to sit down and review the whole thing, and also as a writer's-block-breaker.
It's the folks generating whole codebases with no ability to review or debug that are in deep Monkey's Paw territory.
Larger blocks are also perfect for scripts and tools for personal use, in this case you can just check if it works or not, Claude 3.5 Sonnet usually does not disappoint.
I tried copilot like 8 months ago for supercharged auto complete only, but I wasn't a fan because it was too high latency. I usually liked what it would write, but the second or so it took would really break my flow and had the overall effect of slowing me down. Makes me wonder if a local LLM could be superior here.
It seems to have gotten much faster recently so it might be worth another look. I also found it much slower while working on remote folders (with VS Code at least).
That's good to know, the first time I tried it I was working on remote folders (just the way things are setup at work). Maybe I'll have to try it on my own computer and see.
Who cares? Solve problem, write test case, move on.
It's a huge efficency boon for those of us who realize our jobs are just mechanisms to make money. It sucks if you're into artisinal coding or whatever..
I try LLMs once a month with variations of the same question on a specific library that I use. It hallucinates all the time. I can't use those tools as long as they don't give me the answers I need.