GitHub Copilot available for JetBrains and Neovim
1–10 of 446 posts
Re: GitHub Copilot available for JetBrains and Neovim
#2Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
Re: GitHub Copilot available for JetBrains and Neovim
#3I've been getting a lot more misses than hits with Github Copilot, even when writing elementary math or utility functions; but despite its error I am nevertheless astonished at its approximation of intent.
Very eager to see Github Copilot catchup to some bright line of signal v noise.
Re: GitHub Copilot available for JetBrains and Neovim
#4Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
It is massively improving my productivity, things I couldn’t be bothered to write it does for me.
The thing I find really good is it can predict what I will do next. Say if I have a list of columns in some text somewhere in the project when I write one “df = df.withColumn(“OneItemInList”)”
Copilot will then add the same for all the other items - is really nice
Re: GitHub Copilot available for JetBrains and Neovim
#5Here is a demo of it with Neovim & Codespaces: https://twitter.com/josebalius/status/1453413543232090118
Re: GitHub Copilot available for JetBrains and Neovim
#6Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
Tried it out for a while, and it's clear that it's trying to get people to be faster at writing boilerplate, not get people to write better code.
I'm a bit scared for what this means as I don't think being able to faster write boilerplate is something worthwhile. The example ed_elliott_asc made is one of those examples where instead of fixing things so you don't have to repeat yourself, copilot makes it easy to just live with the boilerplate instead.
Re: GitHub Copilot available for JetBrains and Neovim
#7Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
I only played around with it on OpenAI but it's the same model as far as I know. It's pretty good at regurgitating algorithms it's seen before. It's not good at all at coming up with new algorithms.
It's very good at translating between programming languages, including pseudocode.
It can write a lot more valid code much quicker than any human, and in a whole slew of languages.
I haven't had the urge to use it much after playing around with it constantly for a few days, but it was pretty mind-blowing.
Re: GitHub Copilot available for JetBrains and Neovim
#8Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
It’s a dream come true for the script kiddies.
Re: GitHub Copilot available for JetBrains and Neovim
#9Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
I only played around with it on OpenAI but it's the same model as far as I know. It's pretty good at regurgitating algorithms it's seen before. It's not good at all at coming up with new algorithms. It's very good at translating between programming languages, including pseudocode. It can write a lot more valid code much quicker than any human, and in a whole slew of languages. I haven't had the urge to use it much af…
Your response makes me wonder if poisoning the well is possible by submitting code to Github with multiple languages and coding styles. A single file with a function signature written in Javascript and the body written in Python + Ruby. Enough code would surely break the AI model behind it. Unless Copilot has some sort of ingestion validation which wouldn’t surprise.
Re: GitHub Copilot available for JetBrains and Neovim
#10Can any users give their opinion on how it's helping their productivity? What problems are they finding, if any?
It can generate the body of test cases well, especially in BDD frameworks where you write the high-level scenario first to prime it with context. Less tedium encourages me to write more tests.
More verbose languages like C++ become less obnoxious to write in. I know RSI has been mentioned and any tool which cuts down on excessive typing will help with that.
It sometimes reveals bits of the standard library I wasn't aware of in unfamiliar languages. I can write my intent as a comment and then it may pull out a one-liner to replace what I would have normally done using a for loop.
The main downside I've observed is that if I'm not trying to reign it in, it can result in a lot of WET code since it can pattern match other areas of the surrounding code but can't actually rewrite anything that has already been written. It is important to go back and refactor the stuff it produces to avoid this.