“I poisoned my own mind.”
-
@dalias I made a useful product that I'd never make by myself, as it would take months to code. I reviewed the code and steered the clanker from its mistakes. It is a new piece of software. If anyone finds a plagiarized piece of code, I'll be glad to add the credits.
I don't even need to defend myself, the code is free and there are users already.
@dalias there's one significant difference from human written code: the amount of comments. Humans don't document as much as the machine. It helps the machine in adding more code and it helps a human understand the logic.
So, my bald claim is that it's a useful tool that's not going away any time soon, so it's alright to utilize it if you know what you're doing.
-
@glyph @davidgerard @chroma I've wrestled with this problem too and decided that getting mad at every Tom, Dick and Harry who doesn't feel or do the exact same things I do is neither a good use of my energy nor a good way to hold the kinds of meaningful relationships that actually change behaviour.
It's a tough balance to strike because I really don't want to excuse AI as a technology, and there's a lot of justified anger, but it's better to send that anger to people who deserve it and have power over it (read: technology executives, data centre building companies) rather than at people who don't have that power and are just as likely to be victims
@brib @glyph @davidgerard Uh, oh, excusing people because they're weak-minded or surrender to “convenience” is not the way to go, I believe.
-
@dalias there's one significant difference from human written code: the amount of comments. Humans don't document as much as the machine. It helps the machine in adding more code and it helps a human understand the logic.
So, my bald claim is that it's a useful tool that's not going away any time soon, so it's alright to utilize it if you know what you're doing.
@bonkers The kind of comments in LLM codeslop are the opposite of useful. They do not document motivations why something was done the way it was, connections to external contracts, etc. They're imprecise restatement of what's in the code. The same bad types of comments novice human codemonkeys write when told to comment their code better.
-
@bonkers The kind of comments in LLM codeslop are the opposite of useful. They do not document motivations why something was done the way it was, connections to external contracts, etc. They're imprecise restatement of what's in the code. The same bad types of comments novice human codemonkeys write when told to comment their code better.
@dalias I assume you didn't open my link
-
@dalias I assume you didn't open my link
@bonkers Of course I didn't.
-
@bonkers Of course I didn't.
@dalias so, another bold claim without any ground.
-
@dalias so, another bold claim without any ground.
@dalias sorry mate, but you have no fucking clue what you're talking about.
-
@dalias so, another bold claim without any ground.
@bonkers No, it's not a "bold claim". There is no model of reality or how anything works in these systems, only pattern regurgitation in ways that correlate/align with context. If you get any comments that appear to explain motivations, they're copies of someone else's ideas from a similar context, not something reasoned to apply to your code.
The way you support or refute what I'm saying is through examination & analysis of the mechanisms, not examination of the output and whether it looks like what you would expect from human reasoning. "Looks like human reasoning" is the deception working as intended, and if you're trying to assess it from that standpoint, you're falling for the brain rotting program.
-
@bonkers No, it's not a "bold claim". There is no model of reality or how anything works in these systems, only pattern regurgitation in ways that correlate/align with context. If you get any comments that appear to explain motivations, they're copies of someone else's ideas from a similar context, not something reasoned to apply to your code.
The way you support or refute what I'm saying is through examination & analysis of the mechanisms, not examination of the output and whether it looks like what you would expect from human reasoning. "Looks like human reasoning" is the deception working as intended, and if you're trying to assess it from that standpoint, you're falling for the brain rotting program.
@dalias no, I'm just saying that it's a useful tool in an experienced engineer's hands. Everything else is your own assumption.
-
@bonkers The kind of comments in LLM codeslop are the opposite of useful. They do not document motivations why something was done the way it was, connections to external contracts, etc. They're imprecise restatement of what's in the code. The same bad types of comments novice human codemonkeys write when told to comment their code better.
@dalias @bonkers at my job, I work on the open source software of a very famous science project, so people often think they'll "help out" by pointing agents at our codebase. The LLM slop that well-meaning people have started foisting on me and my colleagues almost always has the same thing in common; it's almost always extraordinary and unnecessarily verbose. Pull request descriptions are long paragraphs of repeated information with bold section headers and emoji. Bits of logic that could be a single line are instead broken into multiple hyper-specific functions. function docstrings are useless reframings of exactly what the code says, without actually saying what situations the function should be used for. It's a mental burden that these people dump on us and say "you sort this out, I'm so helpful!" and I just want to reach through the screen and shake their shoulders and tell them that if they actually want to be helpful they can just read our contributing docs and write stuff themselves!
-
@dalias @bonkers at my job, I work on the open source software of a very famous science project, so people often think they'll "help out" by pointing agents at our codebase. The LLM slop that well-meaning people have started foisting on me and my colleagues almost always has the same thing in common; it's almost always extraordinary and unnecessarily verbose. Pull request descriptions are long paragraphs of repeated information with bold section headers and emoji. Bits of logic that could be a single line are instead broken into multiple hyper-specific functions. function docstrings are useless reframings of exactly what the code says, without actually saying what situations the function should be used for. It's a mental burden that these people dump on us and say "you sort this out, I'm so helpful!" and I just want to reach through the screen and shake their shoulders and tell them that if they actually want to be helpful they can just read our contributing docs and write stuff themselves!
@zrb @dalias true, and the only useful thing here would be rejecting such PRs without spending much time on them.
They could, theoretically, utilize the clanker to produce the change, but they should at least be able to understand and summarize it.
My point is, it's a tool. A hammer could also be used for building good stuff and for killing people.
-
@zrb @dalias true, and the only useful thing here would be rejecting such PRs without spending much time on them.
They could, theoretically, utilize the clanker to produce the change, but they should at least be able to understand and summarize it.
My point is, it's a tool. A hammer could also be used for building good stuff and for killing people.
-
@bonkers @dalias that was the first thing we did, and really all that does is weed out the people and automated agents that respect policies, and select for people and agents that don't. Companies already don't care about open source licenses, and don't respect
robots.txtwhen scraping, so it's no surprise they don't respect community policies either. -
@bonkers @dalias that was the first thing we did, and really all that does is weed out the people and automated agents that respect policies, and select for people and agents that don't. Companies already don't care about open source licenses, and don't respect
robots.txtwhen scraping, so it's no surprise they don't respect community policies either. -
-
@dalias no, I'm just saying that it's a useful tool in an experienced engineer's hands. Everything else is your own assumption.
There is no understanding or real logic involved in LLM output. Only dice rolls.
Those comments only say something that plausibly sounds like what the batch of text called a "comment" has been determined to be LIKELY to say.
That's not a guess, that's how the thing works. The LLM is the thing doing the guessing. It isn't capable of understanding or reasoning.
-
@dalias no, I'm just saying that it's a useful tool in an experienced engineer's hands. Everything else is your own assumption.
@bonkers i'm sure there's a tool involved
-
There is no understanding or real logic involved in LLM output. Only dice rolls.
Those comments only say something that plausibly sounds like what the batch of text called a "comment" has been determined to be LIKELY to say.
That's not a guess, that's how the thing works. The LLM is the thing doing the guessing. It isn't capable of understanding or reasoning.
@violetmadder @dalias you just shouldn't use it for things that need reasoning. It's pretty good at standard tasks, so keep it at that.
-
@violetmadder @dalias you just shouldn't use it for things that need reasoning. It's pretty good at standard tasks, so keep it at that.
Comments need reasoning. Code structure needs reasoning.
In those tasks, the plausible mimicry of what's needed is not just insufficient, but dangerous.
-
@violetmadder @dalias life is dangerous. The longer you live, the closer you are to your death.
Hammers and axes are dangerous, they can be used as a weapon.
We just have to admit that the clankers will stick around. We just have to minimize the danger.
