[bowsamic]

I've taken the simple solution: if I want to enjoy programming for programming's sake, I turn copilot off. If I want to be careful and understand the problem and its solution in detail, I turn copilot off. If I simply want to get a toy project done and don't care at all about the implementation process, I might leave it on.

I've had an absolutely magical experience with copilot though. I honestly find it a bit strange when others say it has just been bad for them

[bluGill]

Copilot does very well when I'm solving the same problem I've solved in the past with different parameters. Parse a CAN network packet (8 bytes so they do weird things like 6 bit counters with 2 bytes in byte 3 and the rest in byte 4) copilot can write that and the tests quickly - we have hundreds of different CAN packets we parse so there is a lot of example code to look at. Everything is just different enough to look like boilerplate while not actually being boilerplate. However when I'm trying to write code that isn't a variation of something I've done many times before copilot is not helpful. It can't complete as much and what does complete is wrong often for style reasons (it would be nice if the function it wants to call existed but it doesn't, or does takes some other parameter that it doesn't know)