Loving this comment on that PR: > I'm losing my job right in front of my eyes. Thank you, Father.
Promising results from DeepSeek R1 for code
151–160 of 765 posts
Re: Promising results from DeepSeek R1 for code
#152Given these initial results, I'm now experimenting with running DeepSeek-R1-Distill-Qwen-32B for some coding tasks on my laptop via Ollama - their version of that needs about 20GB of RAM on my M2. https://www.ollama.com/library/deepseek-r1:32b It's impressive! I'm finding myself running it against a few hundred lines of code mainly to read its chain of thought - it's good for things like refactoring where it will thi…
Re: Promising results from DeepSeek R1 for code
#153Can’t help but wonder about the reliability and security of future software.
Given the insane complexity of software, I think people will inevitably and increasingly leverage AI to simplify their development work.
Nevertheless, will this new type of AI assisted coding produce superior solutions or will future software artifacts become operational time bombs waiting to unleash the chaos onto the world when defects reveal themselves?
Interesting times ahead.
Re: Promising results from DeepSeek R1 for code
#154> 99% of the code in this PR [for llama.cpp] is written by DeekSeek-R1 It's definitely possible for AI to do a large fraction of your coding, and for it to contribute significantly to "improving itself". As an example, aider currently writes about 70% of the new code in each of its releases. I automatically track and share this stat as graph [0] with aider's release notes. Before Sonnet, most releases were less than…
Hello... Is it possible to use aider with a local model running in LMStudio (or ollama)? From a quick glance i did not see an obvious way to do that... Hopefully i am totally wrong!
In the left bar there's a "connecting to LLMs" section
Check out ollama as an example
Re: Promising results from DeepSeek R1 for code
#155Earlier quoted context omitted.
Why though? I'm worried these technologies may take my job away and make the balance between capital and labor even more uneven. Why should I be happy?
You won't be happy doing a robot's job either, at least not for long. In the ideal case, we won't be dependent on the unwilling labor of other humans at all. Would you do your current job for free? If not -- if you'd rather do something else with your productive life -- then it seems irrational to defend the status quo. One thing's for certain: ancient Marxist tropes about labor and capital don't bring any value to t…
Re: Promising results from DeepSeek R1 for code
#156Earlier quoted context omitted.
Eh it performed a 1:1 conversion of ARM NEON to wasm SIMD, which with the greatest will in the world is pretty trivial work. Its something that ML is good at, because its the same problem area as "translate this from english to french", but more mechanistic This is a task that would likely have taken as long to write by hand as the AI took to do it, given how long the actual task took to execute. 98% of the work is f…
Every time AI achieves something new/productive/interesting, cue the apologists who chime in to say “well yeah but that really just decomposes into this stuff so it doesn’t mean much”. I don’t get why people don’t understand that everything decomposes into other things. You can draw the line for when AI will truly blow your mind anywhere you want, the point is the dominoes keep falling relentlessly and there’s no end…
I draw the line, when the LLM will be able to help me with a novel problem.
It is impressive how much knowledge was encoded into them, but I see no line from here to AGI, which would be the end here.
Re: Promising results from DeepSeek R1 for code
#157Earlier quoted context omitted.
Do we know how do these distilled versions perform in benchmarks?
DeepSeek published a bunch of benchmarks when they released the models: https://github.com/deepseek-ai/DeepSeek-R1?tab=readme-ov-fil... I'd like to see detailed benchmarks run by other unaffiliated organizations.
so basically there is not much reason to go beyond DeepSeek-R1-Distill-Qwen-32B, at least for coding tasks
Re: Promising results from DeepSeek R1 for code
#158> 99% of the code in this PR [for llama.cpp] is written by DeekSeek-R1 I hope we can put to rest the argument that LLMs are only marginally useful in coding - which are often among the top comments on many threads. I suppose these arguments arise from (a) having used only GH copilot which is the worst tool, or (b) not having spent enough time with the tool/llm, or (c) apprehension. I've given up responding to these.…
> Our trade has changed forever, and there's no going back. When companies claim that AI will replace developers, it isn't entirely bluster. Jobs are going to be lost unless there's somehow a demand for more applications This is a key insight - the trade has changed. For a long time, hoarding talent - who could conceive and implement such PRs - was a competitive advantage. It no longer is because companies can hire a…
Do you have a link to that?
Re: Promising results from DeepSeek R1 for code
#159Earlier quoted context omitted.
LLMs are incredibly useful for coding, if you learn how to apply them effectively. You have simply chosen to dismiss or 'give up' on that fact.
They are a useful tool, but not 'incredibly useful'. The simple, repetitive code in this example is what they are good at. It's like 1% of what I do working on products. Writing code isn't even that impressive, the whole job is figuring out exactly what people want.
Re: Promising results from DeepSeek R1 for code
#160Earlier quoted context omitted.
> I hope we can put to rest the argument that LLMs are only marginally useful in coding - which are often among the top comments on many threads. I suppose these arguments arise from (a) having used only GH copilot which is the worst tool, or (b) not having spent enough time with the tool/llm, or (c) apprehension. I've given up responding to these. Look at the code that was changed[0]. It's a single file. From what I…
"Yeah, but LLMs can't handle millions of lines of crufty old Java" is a guaranteed reply any time this topic comes up. (That's not to say it isn't a valid argument.) Short answer: LLMs are amazingly useful on large codebases, but they are useful in different ways. They aren't going to bang out a new feature perfectly first time, but in the right hands they can dramatically accelerate all sorts of important activities…
That's not at all what the GP was saying, though:
> There's no need to implement half the code, realize the requirements weren't specified properly, and go back and have a conversation with the PM about it. Which is, you know, what developers actually do.