> Other clues include highly structured comments with multiple headings, unnecessary comments in code, gratuitously defensive programming, and the use of emoji characters.... In general, if something in a pull request seems uncannily cheerful or meticulous then you could be looking at AI-generated content.
So, get rid of formatting, throw in an innocent grammatical mistake, intentionally omit an obscure corner case while alluding to an existential crisis for taking compromises and you're good to go!
I believe in linking over copy & paste, in particular when I want neither to quote the full FAQ nor editorialize by selective quoting. By reading the FAQ, people can form their own opinion on it.
> Other clues include highly structured comments with multiple headings, unnecessary comments in code, gratuitously defensive programming, and the use of emoji characters.... In general, if something in a pull request seems uncannily cheerful or meticulous then you could be looking at AI-generated content.
So, get rid of formatting, throw in an innocent grammatical mistake, intentionally omit an obscure corner case while alluding to an existential crisis for taking compromises and you're good to go!
There is a more helpful way to reply, that includes this text.
I believe in linking over copy & paste, in particular when I want neither to quote the full FAQ nor editorialize by selective quoting. By reading the FAQ, people can form their own opinion on it.