I've been ruminating on this.
-
@mos_8502 Just so we're clear (not trying to be disagreeable, simply curious), are you saying you think all IP protections should be abolished?
@jaredwhite I would personally replace current copyright and patents with mandatory donation to the public domain, with legal requirements for the release of source code and schematics of any work or device - coupled with universal basic income and lifetime bonuses paid to creatives for their output being used.
-
@mos_8502 the funniest thing is that it can find common bugs if you tell it specifically what to look for. It'll even find those bugs in code it just wrote, if told to do so. The horror is that most vibe coders don't understand that the common bugs, including common security bugs, are gonna creep in and you're going to have to hunt them and protect against them.
I've come to the conclusion that the job of a vibe coders is policing the AI via overwhelming use of verification tools.
@swelljoe I feel there's a useful and productive distinction to be made between a "vibe coder" and someone just integrating it into their workflow as one more tool in the toolbox.
In my experiment, I found that ChatGPT Codex does a wonderful job working with Git in fairly complex ways, for example.
-
@swelljoe I feel there's a useful and productive distinction to be made between a "vibe coder" and someone just integrating it into their workflow as one more tool in the toolbox.
In my experiment, I found that ChatGPT Codex does a wonderful job working with Git in fairly complex ways, for example.
@swelljoe Like, "Back up three commits, extract this change, and apply it to the current head of this other branch" level complex.
-
@jaredwhite I would personally replace current copyright and patents with mandatory donation to the public domain, with legal requirements for the release of source code and schematics of any work or device - coupled with universal basic income and lifetime bonuses paid to creatives for their output being used.
@mos_8502 Interesting! I would love to live in that world. 😅
All I've been saying is a world where LLMs live as if copyright & IP protection isn't a thing (they can steal it all!) whereas the rest of us get thrown in jail for committing a similar offense is the worst of all possible worlds.
-
@mos_8502 Interesting! I would love to live in that world. 😅
All I've been saying is a world where LLMs live as if copyright & IP protection isn't a thing (they can steal it all!) whereas the rest of us get thrown in jail for committing a similar offense is the worst of all possible worlds.
@jaredwhite On the bright side, LLM output is not copyrightable under current law.
-
Personally, I think LLMs are very likely more suited to generating code than they are English prose. And the compile/error/fix loop provides feedback that the machine can use to catch its own errors, something it can't do in English prose.
But untrained, inexperienced users who don't or won't understand what's really going on here are being stunted in their growth by overusing and misusing these things.
@mos_8502
There's an awfully big difference between code that compiles and code that *works*. -
@mos_8502
There's an awfully big difference between code that compiles and code that *works*.@RealGene Truth -- only a human can determine if the code works. Test frameworks only go so far.
-
@swelljoe I feel there's a useful and productive distinction to be made between a "vibe coder" and someone just integrating it into their workflow as one more tool in the toolbox.
In my experiment, I found that ChatGPT Codex does a wonderful job working with Git in fairly complex ways, for example.
@mos_8502 yeah, the machines are now better than me several categories of problem, and I'm using them a bunch...but, I'm still keeping a gun by the computer in case it makes any weird noises.
-
@mos_8502 yeah, the machines are now better than me several categories of problem, and I'm using them a bunch...but, I'm still keeping a gun by the computer in case it makes any weird noises.
@swelljoe "Go digging in this codebase and find some bugs" is somehow a reasonable prompt now.
-
@swelljoe "Go digging in this codebase and find some bugs" is somehow a reasonable prompt now.
@mos_8502 that can backfire. It'll invent bugs if there aren't any to find. Somebody blogged about prompting "improve the quality of the code in this project" over and over, and it ended up adding hundreds of thousands of lines of code. It doesn't know how to say "no" or "I don't know". Gotta be specific. "Check for common security bugs" is probably not dangerous, but I'd still feel better about telling it to use all available static analysis tools to find common security bugs.