Interesting, I'm on the same page regarding the first paragraph of yours. And exactly because of this I dislike using Copilot, since most of the time it will provide a completion which has issues. Not necessarily bugs, but the completion does something slightly off or doesn't (or does) consider an edge case different to what is intended.
This detracts me quite a bit from writing code. I don't want to supervise my junior co-developer, I want to get something done - this is why I also, like the author, enable CoPilot only selectively. On the other hand, using ChatGPT-4 (as in chat.openai.com) for creating large-ish chunks of code after discussing the general idea and refining it for a while is a god-send.
If I know what I want to write, Copilot will really speed up my process of writing this. If I don't know what I want to write, ( how to structure the function, how to put the comment, etc...) then asking Copilot for suggestions is distracting.
So I make sure I know what I want to write before I hit the keyboard.
That's true, Copilot is often hit or miss but it's mostly been a hit for me, so the additional parsing of suggestions is acceptable to me as, in aggregate, it speeds up my iteration time.
This detracts me quite a bit from writing code. I don't want to supervise my junior co-developer, I want to get something done - this is why I also, like the author, enable CoPilot only selectively. On the other hand, using ChatGPT-4 (as in chat.openai.com) for creating large-ish chunks of code after discussing the general idea and refining it for a while is a god-send.
YMMV, as always.