Ask HN: Is there a better and more affordable AI coding tool than Claude?
The article discusses the use of AI coding tools, specifically Claude, and their limitations. The author suggests that while Claude is strong for reasoning over larger code changes, its cost can be prohibitive for daily use. The author recommends using Claude selectively and investing in tooling around the repository itself to improve productivity.
- ▪Claude is strong for reasoning over larger code changes but can be costly for daily use.
- ▪Combining a cheaper model with a stronger model for specific tasks can be more effective.
- ▪Tooling around the repository is crucial for improving productivity with AI coding tools.
Opening excerpt (first ~120 words) tap to expand
I would not look only at the model, but at the workflow around it.Claude is still very strong for reasoning over larger code changes, but the cost becomes painful if you use it as a constant pair programmer. For daily work I usually get better results by combining a cheaper model/tool for small edits with a stronger model only for architecture, refactors or debugging.The real missing piece for me is not another chat UI, but a clean way to make repos more predictable: detect the stack, know how to run tests, know how to build, and avoid guessing commands. Most AI coding tools still waste time because they do not understand the project’s operational surface before editing.So my answer would be: use Claude selectively, but invest more in tooling around the repo itself.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.