I would argue a programmer who doesn't notice the encoding issue when looking at this code would be the same kind of programmer who would write this kind of enc

I would argue a programmer who doesn't notice the encoding issue when looking at this code would be the same kind of programmer who would write this kind of encoding issue. You definitely need to manage copilot's generated code to meet your requirements, the key is that massaging takes way less time than writing it all from 0. Copilot is, as the name suggests, a human-in-the-loop system. For me, this is definitely a piece of the future of coding, and it doesn't change coding from a creative endeavour. It's just the difference between "let me spend five minutes googling this canvas API pattern I used 5 years ago and forgot, stumble through 6 blogs that are garbage, find one that's ok, ah right that's how it works. Now what was I doing?" To just writing some prompt comment like "// fn to draw an image on the canvas" and then being like "ah that's how it works. Tweak tweak write write". For me the creativity is in thinking up the high level code relationships, product decisions, etc. I don't find remembering random APIs or algos I've written a million times before to be creative.