Live data from Hacker News

AI tooling must be disclosed for contributions

github.com

471–480 of 482 posts

Re: AI tooling must be disclosed for contributions

#471
post #382

Earlier quoted context omitted.

Eh, they figured out how to copyright photographs, where the human only provides a few bits (setting up the scene, deciding when to pull the trigger etc); so stretching a few bits of human input to cover the whole output of an AI should also be doable with sufficiently well paid lawyers.

It's already been done. https://en.wikipedia.org/wiki/Generative_artificial_intellig...

Nice, thanks!

Re: AI tooling must be disclosed for contributions

#472

Earlier quoted context omitted.

If you removed all PR’s from the world that included copy-pasted code from stackoverflow that wasn’t mentioned, you’d be removing a LOT of PR’s. It’s not even considered a problem to copy and paste code from stackoverflow among most devs as long as you have reviewed it and modified it where necessary for your purposes. AI should be treated like that, if it’s not, people will just hide it and do it anyway.

Just because many developers are irresponsible in their approach to incorporating others’ works doesn’t change how intellectual property actually works, and any project that actually cares (whether open or proprietary) will ensure that people understand their responsibilities. What you’re saying is essentially the code equivalent of “I found this image via Google search so of course it’s OK to put into a presentation…

Your argument breaks down when you realise that doing simple operations will result in the exact same code anyway. If I want to pull the first word from a string, whether I write it myself or copy and paste it from stack overflow we’re going to likely literally result in the exact same line of code. It’s not the same as an image from google images, because that image has a far higher chance of being unique.

You can talk about how we should act and be all high and mighty all you like, but it’s just burying your head in the sand about the reality of how code is written.

Also, technically, I never said this made it perfectly ok. It’s just that it’s the reality we live in and if we got rid of everyone doing it we’d have to fire 99% of programmers.

Re: AI tooling must be disclosed for contributions

#473

Earlier quoted context omitted.

Just because many developers are irresponsible in their approach to incorporating others’ works doesn’t change how intellectual property actually works, and any project that actually cares (whether open or proprietary) will ensure that people understand their responsibilities. What you’re saying is essentially the code equivalent of “I found this image via Google search so of course it’s OK to put into a presentation…

Your argument breaks down when you realise that doing simple operations will result in the exact same code anyway. If I want to pull the first word from a string, whether I write it myself or copy and paste it from stack overflow we’re going to likely literally result in the exact same line of code. It’s not the same as an image from google images, because that image has a far higher chance of being unique. You can t…

I’ve been in this industry 30+ years working for both very small companies and some of the largest. I thus have a pretty good understanding of the reality of how code is written, and you’re the one burying your head in the sand: Companies care about the provenance of what you write, and if you lie about that—whether explicitly or through omission—and it’s discovered, you’re going to be in a world of hurt since you may be exposing the company to liability and also violating your employer’s trust.

Re: AI tooling must be disclosed for contributions

#474
post #142

Earlier quoted context omitted.

Training an AI model is not the same as using an AI model.

Publishing pirated copies of books on libgen isn't the same as downloading pirated copies of books from libgen. Neither is legal.

Many jurisdictions outlaw sharing but not copying. Downloading is legal in those places but publishing is not.

Re: AI tooling must be disclosed for contributions

#475

Earlier quoted context omitted.

Junior developers are entering a workforce where they will never not be using AI

> Junior developers are entering a workforce where they will never not be using AI This remark seems very US-centric to me. In my observation, many people are much more skeptical concerning whether AI is actually useful beyond some gimmicky applications.

Half the planet is more AI-positive than the US. Something like only 4% of Chinese people are concerned about AI while around half of Americans are concerned about AI.

Re: AI tooling must be disclosed for contributions

#476

Earlier quoted context omitted.

> ...you need to evaluate quality not process. Respectfully, Mr. Redis, sir, that's what's going on. I don't see any reason to make a video about it. From the PR that's TFA: "In a perfect world, AI assistance would produce equal or higher quality work than any human. That isn't the world we live in today, and in many cases it's generating slop. I say this despite being a fan of and using them successfully myself (wit…

"I don't see any reason to make a video about it". This sentence is so wrong in its depth that's difficult to know where to start arguing against it. "The disclosure is to help maintainers assess how much attention to give a PR." For the same reason we should ask how many years contributing have been writing software and in the specific language, as they are also correlated with quality of produced code. "we need to…

There's a world of difference between giving feedback and coaching to a human that might be able to learn from that feedback and use it to do better, and giving feedback and coaching to a LLM that has a human acting as its go-between.

If research continues over the next few decades, these LLMs (and other code-generation robots) may well be able retrain themselves in real-time. However, right now, retraining is expensive (in many ways) and slow. For the foreseeable future, investing your time in providing feedback and coaching intended to develop a human programmer into a better human programmer to an LLM is a colossal waste of one's time.

Re: AI tooling must be disclosed for contributions

#477

Earlier quoted context omitted.

Your argument breaks down when you realise that doing simple operations will result in the exact same code anyway. If I want to pull the first word from a string, whether I write it myself or copy and paste it from stack overflow we’re going to likely literally result in the exact same line of code. It’s not the same as an image from google images, because that image has a far higher chance of being unique. You can t…

I’ve been in this industry 30+ years working for both very small companies and some of the largest. I thus have a pretty good understanding of the reality of how code is written, and you’re the one burying your head in the sand: Companies care about the provenance of what you write, and if you lie about that—whether explicitly or through omission—and it’s discovered, you’re going to be in a world of hurt since you ma…

You’re seriously trying to analogously solve teenage pregnancy by advocating for abstinence.

Look around. Do you see the majority of programmers getting fired for copying a line from stackoverflow or using AI?

You must either work in an ultra high security area or are so removed from the groundwork of most programming jobs that you don’t know how people do anything anymore. I’m not surprised you mentioned 30+ years, because that likely puts you squarely out of the trenches where the development is actually done.

Outside of like, the military or airplane software, companies really don’t care about provenance most of the time, their lack of processes to avoid looking into any of that are absolute PROOF of that. It’s don’t ask don’t tell out there.

You can be delusional all you like, it doesn’t change the reality of how most development is done.

Again, I didn’t say it’s a good thing, it’s just that it is reality.

Re: AI tooling must be disclosed for contributions

#478

Earlier quoted context omitted.

Your argument breaks down when you realise that doing simple operations will result in the exact same code anyway. If I want to pull the first word from a string, whether I write it myself or copy and paste it from stack overflow we’re going to likely literally result in the exact same line of code. It’s not the same as an image from google images, because that image has a far higher chance of being unique. You can t…

I’ve been in this industry 30+ years working for both very small companies and some of the largest. I thus have a pretty good understanding of the reality of how code is written, and you’re the one burying your head in the sand: Companies care about the provenance of what you write, and if you lie about that—whether explicitly or through omission—and it’s discovered, you’re going to be in a world of hurt since you ma…

As a side note, the company I work for actively encourages ai use in development, and this is really quite common now.

Re: AI tooling must be disclosed for contributions

#479

Earlier quoted context omitted.

I’ve been in this industry 30+ years working for both very small companies and some of the largest. I thus have a pretty good understanding of the reality of how code is written, and you’re the one burying your head in the sand: Companies care about the provenance of what you write, and if you lie about that—whether explicitly or through omission—and it’s discovered, you’re going to be in a world of hurt since you ma…

You’re seriously trying to analogously solve teenage pregnancy by advocating for abstinence. Look around. Do you see the majority of programmers getting fired for copying a line from stackoverflow or using AI? You must either work in an ultra high security area or are so removed from the groundwork of most programming jobs that you don’t know how people do anything anymore. I’m not surprised you mentioned 30+ years,…

My last 20 years in the industry were at Apple.

Re: AI tooling must be disclosed for contributions

#480

Earlier quoted context omitted.

You’re seriously trying to analogously solve teenage pregnancy by advocating for abstinence. Look around. Do you see the majority of programmers getting fired for copying a line from stackoverflow or using AI? You must either work in an ultra high security area or are so removed from the groundwork of most programming jobs that you don’t know how people do anything anymore. I’m not surprised you mentioned 30+ years,…

My last 20 years in the industry were at Apple.

Ahh, so you see and accept my points then.
Post reply on HN