I've been using Copilot in my (neo)vim setup for the past few weeks. As a means to stub out things it's fantastic. It's pretty much completely replaced all the things I do with luasnip and snippets. As a stub-out means for more complex stuff it's fine. It can get things started but often takes an obtuse approach to writing the deeper logic.
One place where it's been a huge help is in areas where I'm only slightly knowledgeable. For example: I wanted a rubocop rule that would look for ruby logic in between SQL transaction open and close blocks -- it's a fairly common thing for Rails devs to do, but in a busy code base it's a horrible pattern and I'm looking to burn it down at my company. I'm so-so with rubocop rules so I just had Copilot write it and...uh...the first pass was pretty friggin' good. I had to tweak it a bunch, but Copilot turned what would have been a day of work into an hour.
Now, I learned mostly nothing from having Copilot do that for me. But in this instance, I'm okay staying superficial in Rubocop rule writing -- it's not the core of my job so I don't need to go deeper here. I can see the allure to use it all over the place, but you have to know what you're losing out on not doing it yourself when you invoke it to do something. And, of course, if you don't have some passing knowledge, validating what it writes becomes impossible, as does extending and debugging what it provides.
So is it going to replace me? No. But it sure seems helpful as an augmentation to my brain.
