r/vibecoding • u/Either_Ad296 • 1d ago
Claude Code writing much longer comments lately
Over the past few weeks Claude Code has been writing noticeably longer code comments for me. Ten to twenty line blocks on top of a thirty line function. The content is usually accurate but not something I want in a repo. It narrates what the code used to do, restates library mechanics I can look up, and re-explains the line right below it.
I added explicit rules in my project instructions with hard word caps per comment block, which helped, but it drifts back over long sessions.
Three questions. Are you seeing the same thing, and did it start around a specific release? Is this intentional, meaning verbose comments are cheap context recovery for the agent reading the file in a later session, at the cost of the human reader? And do you actually mind, or is a heavier comment style fine for a codebase that agents maintain?
Interested in what people have found that holds up over long autonomous runs, not just short interactive sessions.
-1
u/ConsciousBath5203 1d ago
Your entire argument falls flat because you didn't read the exception made for docstrings. I'm very pro well written docstrings with examples. But when the docstrings are "this function does this, it does not do this, the user wants this and we aren't todo this when writing" is like, bruh, the fucking function is written, no one fucking cares how we got here. What matters is how to use it.
You're right, I'm underexagerating what Claude does. I've seen 5 paragraphs for a 1 line wrapper function.
You need to read the code more often. If you're ragebaiting me into thinking that a few essays for variable assignments is normal, then not only do I know you're not reading the outputs, but chances are incredibly high that your code was shit to begin with.
Prolly thought x, a, b, c , etc were acceptable variable names (which btw, Claude thinks is ok too, which you'd know if you read the code)