Come on, the LLM language is all over the article:
The workflow I had in mind was deliberately cautious
The code was not the difficult part.
These requirements are not a one-time form to complete and forget. They create an ongoing responsibility around the account, the documented process, community feedback, failures, and potential reversions.
Just a few examples. And yes, Pangram 4 also flags it as 100% LLM written. I don't mind being downvoted or flagged, but I think more people should be aware of the LLM style, even if they're ok with it being used without any disclaimer. It's honestly sad that nowadays people on HN cannot recognize this style.
Perhaps you haven't used LLMs enough, this style is extremely common with Claude. And can you link me a Pangram 4 example where it has lots of false positives? The main reason why Pangram is supposed to be reliable in the first place is that they trade false positives for false negatives.
Comments
Come on, the LLM language is all over the article:
Just a few examples. And yes, Pangram 4 also flags it as 100% LLM written. I don't mind being downvoted or flagged, but I think more people should be aware of the LLM style, even if they're ok with it being used without any disclaimer. It's honestly sad that nowadays people on HN cannot recognize this style.
What about your examples has an llm tell?
I don't trust pangram 4 much. There was a post here earlier confirming it fails for many others.
Perhaps you haven't used LLMs enough, this style is extremely common with Claude. And can you link me a Pangram 4 example where it has lots of false positives? The main reason why Pangram is supposed to be reliable in the first place is that they trade false positives for false negatives.