Poor performance, over tight rate limits, inability to follow prompts suddenly, erratic outputs, which together have combined to increase project costs massively?
Devs Cancel Claude Code En Masse – But Why?
11–16 of 16 posts
Re: Devs Cancel Claude Code En Masse – But Why?
#12Junie is cheaper and built into Webstorm. Also Claude tried to charge my card for months after I've tried to cancel it. Despicable.
Re: Devs Cancel Claude Code En Masse – But Why?
#13Among the worst things that I have a hard time tolerating about Claude: - sycophancy, I'm honestly tired of "You're absolutely right". I need a pair programmer, something that's gonna correct me, provide different ideas, etc. - inability to follow the script. Even though it will tell you you're right, it will still do its thing. Doesn't matter if I spend 2 hours writing a detailed spec file, a todo list, etc, Claude'…
You forgot: "The code is now 100% production ready. All features implemented."
It confidently says this without testing anything or running it.
Placeholder code everywhere, features missing, overall the code ends up not compiling due to the dumbest errors imaginable.
Re: Devs Cancel Claude Code En Masse – But Why?
#14a dev in philipine india and pak will turn out to be cheaper and better than ai
Re: Devs Cancel Claude Code En Masse – But Why?
#15a dev in philipine india and pak will turn out to be cheaper and better than ai
llms*
Re: Devs Cancel Claude Code En Masse – But Why?
#16Among the worst things that I have a hard time tolerating about Claude: - sycophancy, I'm honestly tired of "You're absolutely right". I need a pair programmer, something that's gonna correct me, provide different ideas, etc. - inability to follow the script. Even though it will tell you you're right, it will still do its thing. Doesn't matter if I spend 2 hours writing a detailed spec file, a todo list, etc, Claude'…
You forgot: "The code is now 100% production ready. All features implemented." It confidently says this without testing anything or running it. Placeholder code everywhere, features missing, overall the code ends up not compiling due to the dumbest errors imaginable.
> All features implemented.
Oh right, forgot this one!
Once I had it write a spec file for some work to implement, and the charlatan marked all the todos in the spec as done and said that!