Hacker News new | past | comments | ask | show | jobs | submit
fullstackwife | on: DeepSeek-R1
I was initially enthusiastic about DS3, because of the price, but eventually I learned the following things:

- function calling is broken (responding with excessive number of duplicated FC, halucinated names and parameters)

- response quality is poor (my use case is code generation)

- support is not responding

I will give a try to the reasoning model, but my expectations are low.

ps. the positive side of this is that apparently it removed some traffic from anthropic APIs, and latency for sonnet/haikku improved significantly.

loading story #42773177
mtkd | parent | next
The company has just over 100 employees, built V3 with $5.5M of compute and is quietly releasing tangible product without any hyperbolic PR in advance

They were fairly unknown until 26th Dec in west

loading story #42770401
pmarreck | parent | next
I got some good code recommendations out of it. I usually give the same question to a few models and see what they say; they differ enough to be useful, and then I end up combining the different suggestions with my own to synthesize the best possible (by my personal metric, of course) code.
Gracana | parent
I was looking to see how you're supposed to configure v3, then realized you're probably using the API, and came across this:

> The current version of the deepseek-chat model's Function Calling capabilitity is unstable, which may result in looped calls or empty responses. We are actively working on a fix, and it is expected to be resolved in the next version.

https://api-docs.deepseek.com/guides/function_calling

That's disappointing.