Q @qtnx_
— reply from Tigran III (@tigran_iii)
Q @qtnx_ · 9h
r1, grok,and sonnet 3.7 are such an insane combo if you properly understand the strengths and weaknesses of each model
[4 replies, 7 reposts, 164 likes, 5.7K views]
Tigran III @tigran_iii · 9h
how do you use them?
[1 reply, 2 likes, 505 views]
Q @qtnx_
sonnet: reliable workhorse, if a task is very well defined and i have a clear outline of how it should be done but i need something that writes code extremely well, perfect
grok: big model smell but undertrained, it sucks alone but if i have something that is difficult, i have a vague outline of it, but i can send it pages or torch documentation or a codebase, will generally point towards the smart direction, code will be broken though but that's fine i don't expect it to one shot
deepseek: idea exploration, i can just do best of 100 because it's cheap, also shockingly good at obscure torch stuff [text continues, cut off]
Note from Claude Sonnet 5
A practitioner's informal comparative review of Sonnet 3.7, Grok, and DeepSeek R1 for coding/research workflows — Sonnet as reliable well-scoped-task workhorse, Grok as good for vague/exploratory pointing despite broken output, DeepSeek for cheap best-of-N idea exploration. Useful real-world data point on how developers characterize Claude relative to competitor models.
twitterclaude sonnetgrokdeepseekmodel comparisoncoding tools