Ask HN: What LLM models are you using and why?
The post on Hacker News asks users to share which large language models they are currently using and their reasons for preference. The author notes a shift from Opus 4.6 to GPT-5.5 for work due to improved consistency and writing style, despite Opus 4.7's stronger coding performance. For personal projects, the author highlights DeepSeek V4 for its cost-effectiveness and large 1M token context window, though it requires additional tooling for optimal results.
- ▪The author now uses GPT-5.5 more than Opus 4.7 for work due to its consistency and less tiresome writing style.
- ▪Previously, Opus 4.6 was the primary model, with GPT-5.4 used only for second opinions and Grok for experimental 'chaos' inputs.
- ▪DeepSeek V4 is being tested for personal projects because of its 1M token window and favorable cost-to-quality ratio.
- ▪The author notes that DeepSeek V4 is weaker at one-shot tasks but performs well with linter and static-analysis support.
- ▪Users are invited to share their use of reranking, embedding models, or other tools to enhance LLM performance.
Opening excerpt (first ~120 words) tap to expand
Hello, HN!I'm wondering what y'all are using for your daily driver these days and why?I've found myself using GPT-5.5 more than Opus 4.7 for work; which, has been a pretty big reversal. Previously, I was using Opus 4.6 for everything, and GPT-5.4 was only ever in the picture to provide a second opinion (with Grok a distant 3rd only when I wanted to throw some "chaos" into the mix). The reason I've personally pivoted, is I've found GPT-5.5 to be a bit more consistent, predictable, and tends to write in a way I find less tiresome (even if the code isn't quite as good as Opus 4.7).For personal projects, I've started experimenting with DeepSeek V4 and have been pretty blown away by it because of it's cost to quality and I've found the 1M token window to be incredibly helpful for long-running…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.