So we are not touching the rate limits for those that doesn’t reach them… that’s passive aggressive behavior in my opinion
Claude Code weekly rate limits
651–660 of 724 posts
Re: Claude Code weekly rate limits
#652Anthropic has plans such as $150/user and $150/5-users-but-less-hours-per-user. I could not work out what 2 users or heavy-usage-5-users are intended to do.
There are people that will always try to steal, but there may also be those that just don't understand their pricing.
Also some people keep going forever in the same session, causing it to max out - since the whole history is sent in every request. Some prompting about things like that (your thread has gotten long..) would probably save quite a bit of usage and prevent innocent users from getting locked out for a week.
Re: Claude Code weekly rate limits
#653It turns out that maybe "sell at a loss and make up for it in volume" may not be a solid business strategy. The bait-and-switch continues in the AI bubble.
Re: Claude Code weekly rate limits
#654Earlier quoted context omitted.
It makes me sad that devs start relying on proprietary online services to be able to work. We have been lucky enough to have FOSS tools to do everything and not to have to rely on any specific service or company to work and some of us are deciding to become like Monsanto-addicted farmers who forgot how to do their jobs without something they have to pay every month.
It makes me sad that couriers start relying on third party wheeled machines like cars and motorbikes.
Do their motorbikes stop working in the middle of the week if they make too many deliveries or ask them to pay multiple the base rate for the remaining time?
Re: Claude Code weekly rate limits
#655Apparently people are consistently getting thousands of dollars worth of tokens for their $200/mo sub so this was just obviously unsustainable for Anthropic.
The 95% of users are subsidizing the 5% power users, in theory they could adjust the usage cap dynamically depending on usage vs. total number of subscribers. But of course with a complete lack of transparency it doesn't matter, there is no reason to ever give the benefit of the doubt to a for-profit company.
Re: Claude Code weekly rate limits
#656Earlier quoted context omitted.
There's 2 problems there 1. 'faster' is subjective since you cannot do the same task twice without the second time being biased by the learnings from the first pass 2. While speed might be one measure, I've rarely found speed to be the end goal. Unless you're writing something that's throw away, you'll be reading what was written many times over. Long term maintainability is at odds with speed, in most cases.
You're implying that LLMs make maintainability worst when the opposite could happen if you know how to use the tools.
But the tools are trained on tons and tons of mediocre work and will have a strong tendency to output such. Please share your prompts aimed at preventing mediocre code entering the code bases you work on.
So far almost no code I got from LLMs was acceptable to stay as suggested. I found it useful in cases, when I myself didn't know what a typical (!) way is to do things with some framework, but even then often opted for another way, depending on my project's goals and design. Sometimes useful to get you unstuck, but oh boy I wouldn't let it code for me. Then I would have to review so much bad code, it would be very frustrating.
Re: Claude Code weekly rate limits
#657Who was it that used it 24/7? THIS IS WHY WE CAN’T HAVE NICE THINGS!
Re: Claude Code weekly rate limits
#658Earlier quoted context omitted.
FWIW neither hoard nor ration imply anything about permanence of the thing to me. Whether you were rationed bread or you hoarded bread, the bread isn't going to be usable forever. At the same time whether you were rationed sugar or hoarded sugar, the sugar isn't going to expire (with good storage). Rationed/hoarded do imply, to me, something different about how the quantity came to be though. Rationed being given or…
Isn't hoarding means you can get more bread ? While rationing means: "here is 1kg, use it however you want but you can't get more".
Hoarding doesn't really imply how you got it, just that you stockpile once you do. I think you're bang on rationing - it's about assigning the fixed amount. The LLM provider does the rationing, the LLM user hoards their rations.
One could theoretically ration their rations out further... but that would require knowing the usage to the point to set the remaining fixed amounts - which is precisely whT's missing in the interface.
Re: Claude Code weekly rate limits
#659Earlier quoted context omitted.
Do you mind sharing what industry you’re in where you can fully rely on FOSS? In my industry we’re dependent on MATLAB, Xilinx tools, closed source embedded software and more. To name a few industries: game devs might be stuck with unity, finance quant devs might be stuck with Bloomberg terminals, iOS app devs are stuck with apple’s tooling etc… this isn’t just an LLM problem IMO.
That's a good remark. As my sibling said, backend and web dev. But indeed it always struck me that some developpers decided to become Apple developpers and sacrifice 30% of everything they ever produce to Apple. I would argue that it might a bit different though, because when doing iOS development it's possible that you don't lose you core skill, which is building software, and that you can switch to another platform…
> and sacrifice 30% of everything they ever produce to Apple
In exchange for 500% more paid users
Re: Claude Code weekly rate limits
#660I've gotten some very good use out of LLM's outside of standard U.S. work hours, but I often find that they are quite awful at being helpful coding assistants during my work day. I assume this is due to users competing for resources.
My issue is: a request made during peak usage is treated the same as a request made during low usage times even though I might not be able to get anything useful/helpful out of the LLM during those busy hours.
I've talked with coworkers and friends who say the same.
This isn't a problem with Claude specifically - seems to happen with all the coding assistants.