I'd agree with you if using Copilot meant using and never validating the code that's suggested. Adding it to one's toolbelt can mean coming up with the syntax to then consult the documentation with any questions. But often I imagine it'd just spit out boilerplate code that looks very familiar anyway. I can't come up with the right syntax for various http libraries but I recognize the right one, I just don't want to write it out.
I am using another code completion AI in my IDE, and it’s wonderful.
Why waste brain cells and time on mundane things when my time and attention is better spent thinking about the problem at hand.
And in the future, AI will be able to take over more and more of the time. Eventually we will not be needed at all.
This just sounds like a thought-terminating cliché; what mundane things are you spending your attention on while writing code? Sure, there are times where you might be generating boilerplate, cool, you're paying for a fancy snippet library, except the snippets are potentially malformed so you should check them every time.
To stick with my http library example, figuring out how to pass headers or a json body to a particular library, checking status codes, was it "status_code" or just status, is the body in an attribute called body or content or json or json(). I know this is trivial if you work with the same library over and over again but people are different and some of us work with a wide array of languages or libraries.
I code in Rust but said AI code completion works with some other languages also
https://plugins.jetbrains.com/plugin/12798-tabnine-ai-code-c...