[wongarsu]

With the $20/month claude subscription I frequently run into the session limit in after-work hobby projects. If the majority of your dayjob is actual programming (and not people management, requirements engineering, qa, etc, which is admittedly the reality of many "developer" jobs) the $200/month version seems almost required to have a productive coding assistant

[rhines]

How are you using it? I'm curious if you hit the limit so quickly because you're running it with Claude Code and so it's loading your whole project into its context, making tons of iterations, etc., or if you're using the chat and just asking focused questions and having it build out small functions or validate code quality of a file, and still hitting the limit with that.

Not because I think either way is better, just because personally I work well with AI in the latter capacity and have been considering subscribing to Claude, but don't know how limiting the usage limits are.

[Aurornis]

The $20/month will go fast if you're trying to drive the LLM to do all the coding.

It also goes very fast if you don't actively manage your context by clearing it frequently for new tasks and keeping key information in a document to reference each session. Claude will eat through context way too fast if you just let it go.

For true vibecoding-style dev where you just prompt the LLM over and over until things are done, I agree that $100 or $200 plans would be necessary though.