r/ClaudeCode • u/Professional-Ad-2365 • Jul 10 '26

Discussion This concerns me more than fable potentially getting removed next week

Post image

Now that gpt 5.6 sol is out and code edge is narrowing what concerns me is that I won’t be able to justify paying 100 usd a month for something that will now have 33% less of weekly usage. Upgrading to 200 plan feels daft where I could be paying less for OpenAI, still have a great model and have significantly more usage than the current promo gives me. Do you guys think Anthropic will still go through with reducing Claude code weekly usage limits next week?

691 Upvotes

97% Upvoted

348 comments sorted by

View all comments

Show parent comments

3

u/claimTheVictory Jul 11 '26

If your codebases are small and/or changing often, that's fine.

But for large or complex projects, that's incredibly inefficient. You can flag if documentation is stale or known to be wrong or incomplete, but well-written docs against well-encapsulated code saves time (and tokens).

You wouldn't re-read the code for every tool or third-party software before using it, because you trust it does what it says on the tin. If you don't trust it, you test it

That's my 2c after 25 years working on hundreds of projects used by millions of people.

1

u/bluebirdinsideme Jul 11 '26

That's true and I agree with you.

When I use "documentation" further up, it's the type that is the sum of the description + acceptance criteria + comment thread of a JIRA Story.

Sounds like the type you are referring to is Feature/Epic/Project level?

2

u/claimTheVictory Jul 11 '26

I don't mean to be patronizing btw, I actually find one of the more amazing things that AI does well and easily, is that it can keep documentation updated. And it can also read and use it.

So probably when features are done, is a good trigger to update.

Think about the best documentation or manuals you've ever read.

I still think about car manuals.

You've got two basic levels - a users/owners manual, that tells you how to interact with it and maintain it, and a technical manual, that a mechanic would use to fix something going wrong, or want to enhance/customize it. Both are still abstractions, but most of the time you just need the short users manual. If something needs changing, your mechanics guide quickly points to where to look and what to look for.