[demosthanos]

The biggest consistent tell for LLM writing is when the conversation leaks through into the final prose.

You read along with the text and things seem to be going fine until all of the sudden it starts arguing against a position that no one has actually taken and which doesn't feature elsewhere in the text at all. Then it drops that and goes on for a while before doing the whole thing again about a totally different tangent.

"A tempting option would be to {do this thing that no one would ever actually consider doing}, but it won't work because {reasons}."

You can almost hear the exasperated human on the other side of this conversation telling Claude that it got an idea wrong and then proceeding to not actually proofread the text as a whole before shipping it.

[kevincox]

Yes, I especially see this in code comments. You will get a PR where the comments reference an approach that wasn't the previous state and isn't the state of the PR. You can basically hear the dev telling Claude to take a new approach and now it is so fixated on the old approach being wrong that it litters the whole patch with traces of it despite now being irrelevant.

[greengreengrass]

Exactly this. Most of my time writing code is now not necessarily spent writing the said code, but going through whatever Claude or some other agentic process produced and tidying the comments to be less temporally sensitive to the conversation that produced it.

The problem is that process of not writing the code, but just editing what the LLM produced – and somewhat mindless editing at that (I'm editing comments, not LoC!) – leads to a loss of focus and all the perils of human procrastination that entails (hello, writing comments on HN).

I've tried to prompt Claude et al. not to do this - but whatever I've tried so far, even meta-prompting it to ask why it ignored my instructions, it doesn't work, doesn't stick, and I can't find a good way to stop it.

[unselect5917]

>You read along with the text and things seem to be going fine until all of the sudden it starts arguing against a position that no one has actually taken and which doesn't feature elsewhere in the text at all. Then it drops that and goes on for a while before doing the whole thing again about a totally different tangent.

This just sounds like a typical wikipedia article to me. Where it describes something, and then some editor who disagreed chimes in, "However...." and completely contradicts it.

Learning that Nile Red reads wikipedia articles to sleep made me realize that's why he constantly says it in his videos. Love the dude's content, but lol

[jcattle]

The thing is that LLMs can only ever go forward. It might go into one direction, once that direction is in the context it will realize that it doesn't work, but can't delete. So it has to backtrack (or double down, see the whole seahorse emoji breakdown).

[terabytest]

This one honestly drives me nuts.

Another issue I had recently is one of the subagents made up a bunch of meaningless jargon and Claude gladly repeated it to me with no definition and completely assuming I was coming along for the ride.

[Terretta]

Yes, it's like corrective scar tissue in the final output.