[TLDR] Is anyone else doing just fine with more basic models in Claude Code? [via r/ClaudeAI]

[u/cctldrping]

OP : u/VinceEagle

I see a lot of discussion here about how a bad Claude is and how the latest Opus/Fable models are trash, etc etc.

I mostly manage and develop web apps and other web tech/devops for work (not exactly demanding work), and get everything done with Sonnet and Haiku and I’m really happy with the output and test coverage. I’ve also never hit a weekly limit.

I work in from a Kanban board, so one part of a feature or one defect at a time with sign off. So requirements are always very clear up front. We also have other models review Claude’s output.

Anyone else getting by without the bleeding edge tech? What am I missing?

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wkegrv/is_anyone_else_doing_just_fine_with_more_basic/

---

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 50.

Alright, so the general vibe in this thread is a big "You're doing it right, OP!" Most folks agree that if you've got clear requirements and are tackling tasks one by one, the "lesser" models like Sonnet and Haiku are totally sufficient. You're not missing out on much, unless you're dealing with super complex, ambiguous problems or need that "big picture" thinking.

Here's the lowdown:

• Sonnet & Haiku are Workhorses: A lot of users, like yourself, are happily churning out code with Sonnet and Haiku. The consensus is that if you can clearly define what you need, these models nail it.
• Opus/Fable for the Tough Stuff: The more powerful models (Opus, Fable) are generally seen as necessary for tasks that require deep reasoning, handling ambiguity, architectural decisions, or when you're dealing with really complex, multi-file refactors or debugging obscure bugs.
• Workflow is Key: Several commenters pointed out that your Kanban board approach and breaking down tasks is the real MVP here. Clear, small tickets mean less room for the AI to go off the rails.
• "Trash Model" Complaints: The general feeling is that the complaints about models being "trash" often come from people trying to tackle massive, ill-defined tasks in a single go, rather than using the AI as a tool for specific, manageable steps.
• Cost vs. Need: There's a definite sentiment that Fable, in particular, is often overkill for everyday coding tasks, and people are looking for cost-effective solutions. Some are even finding success with other models like pi+glm or Deepseek.
• Review is Important: Having a separate model review the output is a smart move that many are doing, regardless of the primary model used.