I remember last year there was a lot of buzz and discussions around Github Copilot and it's impact on day to day life of software engineers. Recently noticed that Github Copilot is out of pilot and would be charging money for it soon. With this I was wondering :<p>* Is someone actually using Github Copilot for day to day work?<p>* How often do you use it to write parts of the production code?<p>* What are the use cases for it?<p>* Is it worth it?
It offers a free trial so you can try it for yourself. It's very easy to use and to setup.<p>My impression is that most developers will find it useful as a better code completion and even code documentation tool. Of course, it doesn't replace actually reading and writing code but just writes the boilerplate to speed things-up.<p>Some people don't like it because it makes the actual coding part faster and so they probably feel threatened in some way but the actual coding is actually not the most important part of a software engineer's job (design is the more important part) and as Copilot shows can be automated in a sense already.
I've been experimenting with it.<p>All I can really say is that there is some utility in its completions. But I found that you still have to go through everything it comes up with, because there is a lot of cruft out there that it will happily give to you.<p>As long as you are really precise with your comments and how you structure your code and comment prompts, it seems to do really well. Almost like magic. But it easily goes off on tangents, quite like how you can get your cell phone text messenger to produce crazy sentences by prompting it with a word and accepting completions as-is.<p>Also, it is all too easy to send it into a loop where it continually repeats lines or complete code sections it has already produced.<p>All the stuff about it going against licenses... I don't know if that is actually the case, BUT it is important to note that Github has standardized licenses for the repos, and therefore there is absolutely no excuse if co-pilot isn't obeying them. They're part of Github's work flow!<p>Until I see something that I know came attached to a license that wouldn't allow it, I'm not falling for that particular claim. I would expect them to obey the individual licenses that Github provides each repo.<p>Is it worth it? Not yet. But I have no doubt it will be. I have another month to try it free. But I have a feeling I'll just let it slide as a novelty item I once worked with. I see its potential, and I think it is an amazing toy. But if I was developing co-pilot, I would handle it considerably differently.
Thanks for the reminder to cancel my subscription...<p>I found it getting in the way of the default vscode completions - particularly around auto-import of modules.
No. Not useful if you're half competent. Not ethically/morally justifiable at all.<p>See: <a href="https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=true&query=Copilot&sort=byPopularity&type=story" rel="nofollow">https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=tr...</a>
Yes. I like it, it's great. It often shows me novel ways of solving problems, given those are small enough. It won't generate an entire file for you but it can generate a substantial amount of boilerplate that is very useful for rote CRUD operations.<p>Regarding the ethical aspect, that's simply not something I think about. It's a tool like any other, it's like saying Stack Overflow is unethical because people copy and paste from it. Copilot is merely generating what you would've written anyway from looking at SO and documentation.