Earlier quoted context omitted.
Claude not only writes verbose comments, it also writes comments about how things used to work when refactoring. That might have a place in version control comments, but not in the code.
This speaks to the general problem with using LLMs for writing. The audience they are writing for us you, but you're trying to write for a totally different audience. In code, this manifests as comments in the code that are hyperspecific to the conversation you are having, and not the long term benefit of having those comments in the code. I see this in docs a lot. I've been reading a lot of docs these days where it…
Claudette: Make Claude stop talking like a BuzzFeed article
151–160 of 254 posts
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#152Earlier quoted context omitted.
This or you just repeat the initial prompt every 200k tokens
Which gets you to the point where the whole thing is.. still unreliable. Generative text engines are going to generate. This calls for real enforcement in deterministic pre-edit hooks. And here is where naive people will say something like "Why do I care if robots shit all over the codebase? Code is for machines, I don't expect to deal with it much now". But really externalized CoT like this confuses machines too, wa…
The current output style does work, but it’s a Sisyphean task to tweak it constantly only to find out that CC adhere’s to only 75% of it, no matter what…
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#153Re: Claudette: Make Claude stop talking like a BuzzFeed article
#154Earlier quoted context omitted.
Thanks, this sequence of 33 words alone was enough to give me a searing migraine.
Glad to know it worked. Still pending: the assumed-defaults research track plus the validation-only build phase D demanded — your call on whether to start one now or deploy tonight’s campaign to surface any wrinkles the spec drifted on
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#155Earlier quoted context omitted.
This speaks to the general problem with using LLMs for writing. The audience they are writing for us you, but you're trying to write for a totally different audience. In code, this manifests as comments in the code that are hyperspecific to the conversation you are having, and not the long term benefit of having those comments in the code. I see this in docs a lot. I've been reading a lot of docs these days where it…
I don’t even think comments are useful at all given AI. I can ask my AI to explain a piece of code if I am stuck and I will get a reply in context of what I am looking for.
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#156For those of us who don't want to pay for Gemini tokens, what would be the best local LLM to use for this? (A model that can run reasonably well in a ~24GB MacBook.)
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#157Re: Claudette: Make Claude stop talking like a BuzzFeed article
#158Earlier quoted context omitted.
Claude will end the conversation if you berate it when it screws something up.
Why berate an LLM? That doesn't sound healthy. Sure, it's a machine, but it's simulating a social interaction - being a jerk to it could bleed over into interactions with real people. Also, Westworld? These violent delights have violent ends ? Perhaps there's a tinge of Pascal's wager to it, but I prefer to be courteous to the rapidly improving synthetic intelligences.
Re: Claudette: Make Claude stop talking like a BuzzFeed article
#159I've started giving these instructions and I think I've been much more successful in generating clear output: Comment blocks are Limiting the number of words is the strongest factor in cleaning up the output, IMO. For older code I've instructed it to delete all the comments, and then I re-comment it using a new session and these guidelines, asking it to rejustify the need for every comment to itself.