I think that "you cannot use Copilot" would be sliding down into a bad place, where lots of developers use it but have to lie about using it, and the ones who d

I think that "you cannot use Copilot" would be sliding down into a bad place, where lots of developers use it but have to lie about using it, and the ones who do that and get away with it seem to be the most productive so everyone else feels they have to lie and use it also. Holding developers accountable for the code that they write, whether using Copilot or not, seems a lot more practical. By the way, whether or not "reducing keystrokes" is the right way to think about code productivity is worth thinking about. Thinking carefully about what you need to do for 10 or 15 minutes before starting, can not uncommonly avoid a lot of code by thinking of a more elegant/tidy way to do whatever it is that needs doing. "More haste, less speed".