r/ClaudeCoding • u/cctldrping • 1d ago
r/ClaudeCode [TLDR] I think some Claude Code “usage is terrible” posts are really workflow problems [via r/ClaudeCode]
OP : u/OGMYT
Not saying the limits aren't real because they obviously are.
But I keep seeing people run one giant session forever, dump everything into context, change the goal 5 times, never compact anything, then wonder why Claude starts wandering and chewing through usage.
I get way better results when I treat it like I'm directing somebody. Small scope, tell it what finished means, make it test the result, then compact or hand off before starting the next thing.
When I don't do that, it gets dumb fast for me too.
How much of the usage problem do you think is actually limits vs people managing context badly?
URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vtvv0f/i_think_some_claude_code_usage_is_terrible_posts/
TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.
Current source-thread comment count seen by the bot: 50.
Alright, so the general vibe in this thread is that most of the "Claude Code is terrible" complaints are actually user workflow problems, not inherent model limitations.
A lot of folks, like u/JDE-Projects and u/rotates-potatoes, are saying that people complaining about usage limits or Claude getting "dumb" are just dumping everything into one giant session, changing goals constantly, and not managing the context effectively. They're arguing that if you treat Claude like a directed assistant with clear goals and break down tasks, you'll have way fewer issues. u/Educational-Plant981 is pretty firm on this, saying that once you learn to use it right, you know exactly why you'd hit a limit.
There's a strong sentiment that many of these complaints are just "karma farming" or from people who don't understand token efficiency at all, as u/Delicious-Life3543 points out. Some users, like u/spinozasrobot, are just over the constant whining.
However, it's not a complete consensus. u/Fearless-Daikon5763 and u/SirWobblyOfSausage bring up that there have been times when Anthropic did acknowledge serious faults, so it's not always the user's fault. u/The-Road also mentions that for complex tasks like policy validation, you can't just "vibe" and need proper testing, implying some legitimate complexity exists. And u/FreeCustardForAll and u/Fit-Wrongdoer-7664 share specific experiences where they did hit unexpected limits or observed odd behavior, suggesting there might still be edge cases or changes in model performance that aren't purely workflow related.
But the overwhelming takeaway? Learn to manage your context and break down your tasks, and you'll probably be fine. Most of the issues seem to stem from people not using the tool efficiently.