Another bunch of dead give aways in code bases with READMEs is the repetitive: - "No X, No Y, No Z." pattern - "Here is X - it makes Y" The worst and most obvious one is the constant over use of emoji ticks and crosses.
For calibration purposes, I offer you a pre-LLM README I wrote that includes an em-dash* followed by "No X, No Y, No Z": https://github.com/DavidBuchanan314/stelf-loader *actually a hyphen but it's functioning as an em dash.
It's Not Just X. It's Y
11–20 of 155 posts
Re: It's Not Just X. It's Y
#12Another bunch of dead give aways in code bases with READMEs is the repetitive: - "No X, No Y, No Z." pattern - "Here is X - it makes Y" The worst and most obvious one is the constant over use of emoji ticks and crosses.
For calibration purposes, I offer you a pre-LLM README I wrote that includes an em-dash* followed by "No X, No Y, No Z": https://github.com/DavidBuchanan314/stelf-loader *actually a hyphen but it's functioning as an em dash.
Re: It's Not Just X. It's Y
#13Re: It's Not Just X. It's Y
#14You’re absolutely right. This is the smoking gun. This changes everything.
Re: It's Not Just X. It's Y
#15It's interesting why LLMs generate constructions like this more frequently than they presumably exist in the training set. I wonder if this is some sort of mode collapse caused by post training, and/or maybe because they are training on synthetic data so these things become self-perpetuating and self-amplifying (a feedback loop)?
The lesson for humans worried about being falsely identified as AI is just learn to write better! It doesn't matter where your repertoire of phrasing comes from (copying AI or not), but one of the basic rules of writing is not to repeat yourself unless you are doing so deliberately for a purpose. Go ahead and use "It's not just X. It's Y" if you want to, but if you use it multiple times in the same short piece of writing, then you may deserve to be called out for poor style, if not for being an AI.
Re: It's Not Just X. It's Y
#16Earlier quoted context omitted.
For calibration purposes, I offer you a pre-LLM README I wrote that includes an em-dash* followed by "No X, No Y, No Z": https://github.com/DavidBuchanan314/stelf-loader *actually a hyphen but it's functioning as an em dash.
"Hyphen functioning as an em dash" is an expected human thing as it's what's easy to type. It's specifically an actual em dash which got bulldozed, much to the dismay of those who bothered to put the unicode character in.
Re: It's Not Just X. It's Y
#17Earlier quoted context omitted.
For calibration purposes, I offer you a pre-LLM README I wrote that includes an em-dash* followed by "No X, No Y, No Z": https://github.com/DavidBuchanan314/stelf-loader *actually a hyphen but it's functioning as an em dash.
"Hyphen functioning as an em dash" is an expected human thing as it's what's easy to type. It's specifically an actual em dash which got bulldozed, much to the dismay of those who bothered to put the unicode character in.
Re: It's Not Just X. It's Y
#18Earlier quoted context omitted.
For calibration purposes, I offer you a pre-LLM README I wrote that includes an em-dash* followed by "No X, No Y, No Z": https://github.com/DavidBuchanan314/stelf-loader *actually a hyphen but it's functioning as an em dash.
"Hyphen functioning as an em dash" is an expected human thing as it's what's easy to type. It's specifically an actual em dash which got bulldozed, much to the dismay of those who bothered to put the unicode character in.
Re: It's Not Just X. It's Y
#19Another bunch of dead give aways in code bases with READMEs is the repetitive: - "No X, No Y, No Z." pattern - "Here is X - it makes Y" The worst and most obvious one is the constant over use of emoji ticks and crosses.
I put to you, if you see a trope in AI writing it's because that trope appeared in the training corpus. Therefore, sure, being predjudice against it lets you catch some AI, but you'll also flag human outout. I think that may not be worth it in the end.