@codeinabox The problem with AI being trained on our code is not because the code has inherent value. In most cases, the code *is* being distributed for free, after all.
The *problem* is that it's a violation of licenses - an expression of an author's desire for how their work is used. If an author's work is an extension of themselves, then violating a license is a violation of their autonomy.
@codeinabox My goal in saying "writing code is not the hard part" is to assure people that using a limited visual scripting alternative or "no-code" tool is not the magic bullet they think it is and in fact it will hold them back more than anything. It's not a statement of "it's not impressive to do this well" it's one of "do not be so afraid of this skill, because it's not as unapproachable as you think it is."
@codeinabox When I say some variation of "writing code is not the hard part," what I mean is this: I can get a 9 year old to write a program that compiles and runs. A literal child can achieve "writing code" within an hour. That *specifically* is my bar for "writing code" because, by definition, that's what's happening. However, it's obvious there's a vast difference between what a 9 year old can do in an hour and what a professional software engineer does with 20+ years of experience.
@thekerker@zed Just for your awareness: they do use vibecoding in that project. I have a policy to not run AI generated code if I can avoid it, so I block AI agent accounts on GitHub so I get a big banner whenever I look at a repository with commits from one of them.
@remixtures@tldr.nettime.org This isn't "like" a DDoS attack it IS a DDoS attack.
Virtually every early example of a modern computer attack was originally someone just messing around or making a mistake (the first virus, worm, and DoS all come to mind) and to my knowledge all of those were tried on (and many found guilty to) serious hacking charges, so why shouldn't OpenAI? They shouldn't get to claim "well, your service should have been able to handle a DDoS" or "we're doing it for gain, though."
@codeinabox The problem with AI being trained on our code is not because the code has inherent value. In most cases, the code *is* being distributed for free, after all.
The *problem* is that it's a violation of licenses - an expression of an author's desire for how their work is used. If an author's work is an extension of themselves, then violating a license is a violation of their autonomy.
@codeinabox My goal in saying "writing code is not the hard part" is to assure people that using a limited visual scripting alternative or "no-code" tool is not the magic bullet they think it is and in fact it will hold them back more than anything. It's not a statement of "it's not impressive to do this well" it's one of "do not be so afraid of this skill, because it's not as unapproachable as you think it is."
@codeinabox When I say some variation of "writing code is not the hard part," what I mean is this: I can get a 9 year old to write a program that compiles and runs. A literal child can achieve "writing code" within an hour. That *specifically* is my bar for "writing code" because, by definition, that's what's happening. However, it's obvious there's a vast difference between what a 9 year old can do in an hour and what a professional software engineer does with 20+ years of experience.
@thekerker @zed Just for your awareness: they do use vibecoding in that project. I have a policy to not run AI generated code if I can avoid it, so I block AI agent accounts on GitHub so I get a big banner whenever I look at a repository with commits from one of them.
@remixtures@tldr.nettime.org This isn't "like" a DDoS attack it IS a DDoS attack.
Virtually every early example of a modern computer attack was originally someone just messing around or making a mistake (the first virus, worm, and DoS all come to mind) and to my knowledge all of those were tried on (and many found guilty to) serious hacking charges, so why shouldn't OpenAI? They shouldn't get to claim "well, your service should have been able to handle a DDoS" or "we're doing it for gain, though."