Live data from Hacker News

The Good and the Limitations of Github Copilot

blog.hrithwik.me

101–110 of 144 posts

Re: The Good and the Limitations of Github Copilot

#101
post #98
post #87

Earlier quoted context omitted.

Until a court decides what it does and doesn't do I'm staying clear Here's it outputting Quake code, including handy comments it came up with for each line and even an entire line of commented out code. Maybe it decided it was a good choice to comment it out but still include it I guess Being word for word from the original is just a weird coincidence too I truly wanted it to be as good as it was sold to us too, but…

It didn't copy the entire file for quake - it got the license wrong (which is even worse!) That what I said in my original comment!

[deleted]

Re: The Good and the Limitations of Github Copilot

#102
post #71
post #66

Honestly I just ditched the idea of Copilot the moment it spewed out an entire file of copied code. Nice work on making a markov bot with extra steps GitHub. Please, do take my money..

It never did that. It got the license wrong so it wasn't an exact copy...

Yes; that's even worse.

Re: The Good and the Limitations of Github Copilot

#103
post #98
post #87

Earlier quoted context omitted.

Until a court decides what it does and doesn't do I'm staying clear Here's it outputting Quake code, including handy comments it came up with for each line and even an entire line of commented out code. Maybe it decided it was a good choice to comment it out but still include it I guess Being word for word from the original is just a weird coincidence too I truly wanted it to be as good as it was sold to us too, but…

It didn't copy the entire file for quake - it got the license wrong (which is even worse!) That what I said in my original comment!

Ah I see. I think my perception of your point was altered by you having been downvoted by someone making the text grey (can't read text = bad comment). Sorry about that.

I'll try to avoid letting downvotes bias me in future

Re: The Good and the Limitations of Github Copilot

#104
post #100
post #66

Honestly I just ditched the idea of Copilot the moment it spewed out an entire file of copied code. Nice work on making a markov bot with extra steps GitHub. Please, do take my money..

this is the worse take I've seen so far

Could you explain why or do you just want to feel superior? Both good choices honestly but I'd love to know your actual thoughts

If I'm wrong tell me why and I'll happily reevaluate my opinion, promise :)

Re: The Good and the Limitations of Github Copilot

#107

> Can help you with Email Validation and API Calls It generates a nastily complex regular expression that is hopelessly wrong. Visible at https://www.youtube.com/watch?v=9Pw-Roo_duE&t=404 , here transcribed: /^([\w-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([\w-]+\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})(\]?)$/ For the local part, it requires [\w-\.]+, which excludes many valid characters like everyone’s favourite, +.…

> The author makes no comment on how hideously bad it is, which makes me suspect he didn’t notice, which… yeah, shows the problems of the whole thing.

The author's comments on that "reverse" function are equally bad - https://youtu.be/9Pw-Roo_duE?t=171

It's described as "efficient" but it calls `len` on an unchanging list in 3 places.

Re: The Good and the Limitations of Github Copilot

#108
post #44
post #24

Earlier quoted context omitted.

a == !a There’s several values of a where that yields true (of the top of my head, a = '0' is one of them). Yes, you do need ===.

If someone doesn't understand this then here's why. You need to learn the Six Falsey Things In JavaScript. Everything else when cast to boolean will be true. These six things are What and Why and When And How And Where and Who. Wait, no, that's a totally different list of six... anyways false undefined null NaN 0 "" (empty string) That's it. Since '0' is neither when the negate operator casts it to boolean it'll beco…

> So you are running '0' == 0 which is visibly true...

Crucially, there's the extra step of converting '0' to a number.

Re: The Good and the Limitations of Github Copilot

#109
post #82
post #69

Earlier quoted context omitted.

Isn't "Code you don't understand" the definition of AI/ML?

Zing! But well, depends on the algorithm. Some aren't that complicated to understand, like linear regression. Others, like DNN are basically impossible. But with ML you're at least always testing the code you don't understand in the process of training the parameters. That's better than the minimum effort when using copilot code. And many will just make that minimum effort and release untested code they don't underst…

Well, I think this overestimates people outside the HN echochamber again. Most senior ML people we see in big corps have no clue what they are doing: they just fiddle with knobs until it works. They would not be able to explain anything: copy code/model, change parameters and train until convergence, test for overfitting. When automl was coming a bit I hoped they would be fired (as I do not think they are doing useful work) but nope: they have trouble hiring more of them.

Re: The Good and the Limitations of Github Copilot

#110
post #28

Earlier quoted context omitted.

This is exactly the problem. The regex issue isn’t that it’s not efficient, it’s that it’s wrong. Using this tool to generate code in a problem area you are not qualified to double-check and validate yourself is dangerous.

> Using this tool to generate code in a problem area you are not qualified to double-check and validate yourself is dangerous. I would like this message to be amplified as much as possible. Never write code you do not understand. I am excited about copilot, but also wary of the programming culture these tools will bring in. Businesses, especially body-shopping companies will want to deliver as much using tools in thi…

I think there are a scary amount of programmers (this is their job and they get hired: often they are already seniors) who cannot explain what they copied or even wrote themselves. I have asked guys with 5 years or more job experience why they wrote something they wrote and I get 'because it works'. Sometimes I have trouble seeing why it works and usually it means there are indeed those disastrous edge cases. Copilot will make this worse and has the potential to make it far worse.
Post reply on HN