What confuses me about this stance is that LLMs are basically indistinguishable from any mid-to-low-tier dev. And those we've let into our codebases with no concerns. Hell, some even threw parties inviting in more of them. At least LLMs don't call HR on you when you rightfully tell them that they're full of shit. Though.. well. Claude probably might.
Godot's recent announcement spelled something out clearly: when a mid-tier rando contributes, you can provide feedback to that person and possibly help them grow into being a senior contributor or even a maintainer. That possibility of helping the human behind the code is part of the motivation for doing open-source. Mentoring shitty devs is itself giving back to the community, in a different form than the code itsel…
No LLM Code in Dependencies
91–100 of 120 posts
Re: No LLM Code in Dependencies
#92Earlier quoted context omitted.
I think you're wrong. And I think that FOSS is our last best hope to keep software under the control of the individual. The sloppers are diving head-first into a world where not knowing how a basic idea translates to code is embraced. This is not true of every slopper, but it is true of enough that sloppers are a threat.
I hear you, but again there are a lot of assumptions in this statement: "sloppers are diving head-first into a world where not knowing". The problem is you've redefined LLM-coding as slopping. "This is not true of every slopper".
I'd venture to say that a large number of developers are using LLM tooling at this point. Not all of those developers are out there generating massive, poorly engineered PRs and wasting project maintainer time. For me there are at least those 3 broad categories of user of LLMs for software development, maybe more if I sat and thought about it for a while.
Re: No LLM Code in Dependencies
#93Earlier quoted context omitted.
I hear you, but again there are a lot of assumptions in this statement: "sloppers are diving head-first into a world where not knowing". The problem is you've redefined LLM-coding as slopping. "This is not true of every slopper".
I find your comment here interesting. The parent never called out LLM-coding, they said "sloppers". If we take that choice of word as deliberate, it stands to reason there's a distinction there between "sloppers" and LLM assisted coding in general. You quoting "This is not true of every slopper" as proof they are equating the two seems like a weakly defended assertion. It's entirely possible there are 3 broad classes…
Re: No LLM Code in Dependencies
#94Re: No LLM Code in Dependencies
#95Earlier quoted context omitted.
LLMs are worse at programming than any dev I've ever worked with. Yes, even $latest_model. They have no understanding or ability to reason, and they make mistakes no human would make. They are, in short, bad at programming.
You've not worked with average developers then, or this is a purely reactionary/emotional statement.
Re: No LLM Code in Dependencies
#96What confuses me about this stance is that LLMs are basically indistinguishable from any mid-to-low-tier dev. And those we've let into our codebases with no concerns. Hell, some even threw parties inviting in more of them. At least LLMs don't call HR on you when you rightfully tell them that they're full of shit. Though.. well. Claude probably might.
LLMs are worse at programming than any dev I've ever worked with. Yes, even $latest_model. They have no understanding or ability to reason, and they make mistakes no human would make. They are, in short, bad at programming.
Re: No LLM Code in Dependencies
#97Was this done by manually reviewing commit messages? I think it would be interesting/useful to have a tool that could use some basic heuristics about LLM generated code to detect code-blobs even if they are not explicitly called out in a commit message.
Apparently, though not very carefully. The "particularly large LLM generated code churn" in the ram library, for example, is the LLM being used to simply git-revert a change that was not originally done by an LLM.
Re: No LLM Code in Dependencies
#98When $llm_company begins asking you to open your wallet to fix every vulnerability, bug, or other breaking issue, instead of the guy in Nebraska doing it for free because someone mentored him, will the economics change? Probably not.
Re: No LLM Code in Dependencies
#99How come all the open source projects are fretting over the copyright status of LLM code but big companies are just vibe coding slop all day for their internal closed source projects without a care in the world?
Spotify is running ads for a design "thing", that's basically a generative AI logo creator. Isn't that one of the few instances that's already been clearly put into law - that you can't copyright AI generated stuff? How can you create a business that's selling uncopyrightable logos (which definitely would need/want to be copyrighted/trademarked)? It's the Wild, Wild West out here.
Re: No LLM Code in Dependencies
#100This is completely infeasible in the age of mythos. The reality is that the velocity is just not going to feasible from a security PoV without leveraging these tools.
In ten years we'll look at human written code like the unreliable garbage it is, and never rely on anything that wasn't at least seriously looked over by an LLM. It won't be even close.