[criley2]

They say that copilot is great but the chatbot was bad because it lacked context, missed nuance, and frequently gave correct-sounding answers that actually weren't great.

That's exactly my experience with copilot. For simple text transformation (see this pattern? Repeat it. See this comment? Make another. See how I'm doing this? Finish it) it's ok but when asked to write any amount of code beyond that, it only writes mediocre good-seeming code that when truly analyzed within the context of the codebase, the feature, the libraries in use, the framework and language... suffers from all the same problems. The number of times I've had to walk a junior through some bad react code that an AI wrote and ask them "what do you think this is doing" and have them shrug at me is ridiculous.

On the bright side, those of us at businesses that still care about quality have a lot of work on our plates cleaning up the AI slop getting pushed into code reviews, so yay job security

[dardarbinks]

No yeah. You're totally right. I also see copilot lacking context, missing nuance, and frequently giving correct-sounding answers that actually aren't great.

I still think copilot is great for me, an experienced programmer who can recognize the bad.

But it is a bit scary that it's also empowering less-experienced end-user programmers to write bad code! It's the same story as our docs bot. AI is a good assistant, but it's not ready for taking over, yet.