2 ms·

I don't really mind copyright at all. But I'm worried automation tools take away my (false) sense of control and the art of coding. Why care about variable nam

I don't really mind copyright at all. But I'm worried automation tools take away my (false) sense of control and the art of coding. Why care about variable naming since AI will generate most names anyway, why care about common libraries if you can always get good implementation for specific use case in a second or two? I know these small details don't matter in the big picture, code exists to do something and if it does, it doesn't matter how it was made.

BeefWellington 4y ago
The library point is especially instructive IMO. Copilot introducing "learned" security issues, for example, is a problem separate from the copyright risk. Currently, it's often a matter of updating a dependency to patch things away. How do you do that when you barely understand the code it helpfully generated for you? People will jump to say "well that's using it wrong" but the reality is if you allow this in your org people will use it this way.