4 ms·

I think my experience mirrors your own. We have access at my job but I’ve turned it off recently as it was becoming too noisy for my focus. I found the tool to

I think my experience mirrors your own. We have access at my job but I’ve turned it off recently as it was becoming too noisy for my focus. I found the tool to be extremely valuable when working in unfamiliar languages, or when doing rote tasks (where it was easy for me to identify if the generated code was up to snuff or not). Where I think it falters for me is when I have a very clear idea of what I want to do, and its _similar_ to a bog standard implementation, but I’m doing something a bit more novel. This tends to happen in “reduce”s or other more nebulous procedures. As I’m a platform engineer though, I’m in a lot of different spaces: Bash, Python, browser, vanilla JS, TS, Node, GitHub actions, Jenkins Java workflows, Docker, and probably a few more. It gives my brain a break while I’m context switching and lets me warm up a bit when I move from area to area.

mlinhares 2y ago
the fact that Copilot hallucinates methods/variables/classes that do not exist in compiled languages where it could know they do not exist is just unbelievable to me. it really feels like people building the product do not care about the UX.
memorylane 2y ago
> (where it was easy for me to identify if the generated code was up to snuff or not). I think you have nailed it with this comment. I find copilot very useful for boilerplate - stuff that I can quickly validate. For stuff that is even slightly complicated, like simple if-then-else, I have wasted hours tracking down a subtle bug introduced by copilot (and me not checking it properly) For hard stuff it is faster and more reliable for me to write the code than to validate copilots code.