Earlier quoted context omitted.
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…
This is called the AI effect - where the goalposts are moved every time an AI system demonstrates a new ability. It's been going on for decades. https://en.wikipedia.org/wiki/AI_effect
Promising results from DeepSeek R1 for code
261–270 of 765 posts
Re: Promising results from DeepSeek R1 for code
#262> 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.…
Re: Promising results from DeepSeek R1 for code
#263Earlier quoted context omitted.
"Jobs are going to be lost unless there's somehow a demand for more applications." That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. I think LLM assistance makes programmers significantly more productive, which makes…
> That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. I worry about junior developers. It will be a while before vocational programming courses retool to teach this new way of writing code, and these are going to be te…
This is a problem that the Computer Science departments of the world have been solving. I think that the "good" departments already go for the "broad knowledge" of theory, systems with a balance between the trendy and timeless.
Re: Promising results from DeepSeek R1 for code
#264Earlier quoted context omitted.
First off I want to thank you for Aider. I’ve had so much fun playing with it and using it for real work. It’s an amazing tool. How do you determine how much was written by you vs the LLM? I assume it consists of parsing the git log and getting LoC from that or similar? If the scripts are public could you point me at them? I’d love to run it on a recent project I did using aider.
Glad to hear you’re finding aider useful! There’s a faq entry about how these stats are computed [0]. Basically using git blame, since aider is tightly integrated with git. The faq links to the script that computes the stats. It’s not designed to be used on any repo, but you (or aider) could adapt it. You’re not the first to ask for these stats about your own repo, so I may generalize it at some point. [0] https://ai…
Re: Promising results from DeepSeek R1 for code
#265> 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…
you're assuming the PR will land:
> Small thing to note here, for this q6_K_q8_K, it is very difficult to get the correct result. To make it works, I asked deepseek to invent a new approach without giving it prior examples. That's why the structure of this function is different from the rest.
This certainly wouldn't fly in my org (even with test coverage/passes).
Re: Promising results from DeepSeek R1 for code
#266For what i can understand, he asked deepseek to convert arm simd code to wasm code. in the github issue he links he gives an example of a prompt: Your task is to convert a given C++ ARM NEON SIMD to WASM SIMD. Here is an example of another function: (follows a block example and a block with the instructions to convert) https://gist.github.com/ngxson/307140d24d80748bd683b396ba13b... I might be wrong of course, but ask…
This. For folks who regularly write simd/vmx/etc, this is a fairly straightforward PR, and one that uses very common patterns to achieve better parallelism. It's still cool nonetheless, but not a particularly great test of DeepSeek vs. alternatives.
Re: Promising results from DeepSeek R1 for code
#267Re: Promising results from DeepSeek R1 for code
#268Earlier quoted context omitted.
"Jobs are going to be lost unless there's somehow a demand for more applications." That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. I think LLM assistance makes programmers significantly more productive, which makes…
> That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. I worry about junior developers. It will be a while before vocational programming courses retool to teach this new way of writing code, and these are going to be te…
Why?
Are they not already?
Re: Promising results from DeepSeek R1 for code
#269> 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.…
Re: Promising results from DeepSeek R1 for code
#270> 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.…
I want to stay in Helix and find a workflow that “just works”. Not sure even what that looks like yet