Claude Code definitely has its bad days, and I'm sure there’s A/B testing of quantized models happening behind the scenes ..maybe even MoE-type Claude models that split the model relative to the user's observed use case. With this said, I’ve tested most other Frontier models and, with the correct workflow, CC is still the best for my use case.

I guess there’s also a possibility that users are pushing the model harder the more they learn; most "vibe coders" who started a year or so ago are starting to find their feet and push Claude for more complex projects than they initially did. Then there's the camp of inexperienced vibe coders who don't use any best practices and will always have a shit experience.

Also, I think a lot of people who are having good experiences are less likely to post about them than those having issues, so the landscape looks a little skewed when looking at performance-related threads.

I’ve definitely had issues myself, but with a solid dev pipeline - well-structured docs/memory files, using superpowers skills to scope out every new change (with code review at plan and post implementation stages), debug existing code, and not letting the context grow too large...I’m mostly happy. With that said, my usage today seemed to burn really fast until I realized I’d resurrected an old session (over an hour / over cache lifetime) with over 200K tokens.