For starters, there's a C++ application written with MFC and an absolute ton of inline assembly and threading (yes, in a 1990's C++ application). I'm porting it to MacOS/Linux currently.
Opus 4.6+ is able to make slow progress, but it takes several revisions per workstream. It requires constant supervision as it often creates convoluted solutions that expand the code in bloated ways. It works, but still requires my constant input.
Fable was able to almost one shot most of the big migrations with very few bugs, and was able to fix those bugs with 1 review pass. I almost didn't believe it. I was able to put it on a task (with dangerous permissions) and come back hours later to see it done, working, and clean.
I tried DeepSeek v4 and it wasn't able to make any meaningful progress at all. It kept creating dangling pointers and had trouble understanding the inline assempbly needed to be replaced if we were to compile for 64 bit. It kept getting stuck and looping on the same problem, without making progress.
What I do use DeepSeek for is lots of my automations on my websites. I find DeepSeek is fantastically cheap and fast and effective as summarization, collation, generating reports, finding and reporting issues from logs, etc. But I haven't found a way to get it to effectively port 90's C++ code to modern, cross-platform standards. But I want to be clear- I really like DeepSeek and use it wherever I can.. I mean.. it's so affordable!
I was building a cli tool that showed a graph of git commits, kind of like git log --graph, and deepseek v4 simply could not figure out a specific ui quirk where things weren't lining up correctly. I spent like $0.10 and 30 minutes trying to figure it out on deepseek.
Then I had deepseek summarize the bug, gave it to Opus, and it solved it in $1.12 and five minutes.
Fun fact, I was trying this afternoon Deepseek vs Opus 4.8 high, and I was surprised at how good Deepseek was. It outperformed Opus 4.8 on multiple occasions.
Found just later I was using v4 flash and not pro (for mistakenly setting the model to deepseek-chat and not v4-pro).
There are aspects about Deepseek I don't like though, when pushed against it will eagerly bend instead of reasoning and advocating for his points, something Opus 4.7 and later models started doing a lot (even when wrong).
It is, and I love it, but it isn't capable of performing the tasks I've been giving to Opus, let alone Fable.
Don't get me wrong, I use it, it's fast-smart-and affordable. But not suitable for all tasks.
What kinds of tasks are you finding deepseek v4 incapable of?
For starters, there's a C++ application written with MFC and an absolute ton of inline assembly and threading (yes, in a 1990's C++ application). I'm porting it to MacOS/Linux currently.
Opus 4.6+ is able to make slow progress, but it takes several revisions per workstream. It requires constant supervision as it often creates convoluted solutions that expand the code in bloated ways. It works, but still requires my constant input.
Fable was able to almost one shot most of the big migrations with very few bugs, and was able to fix those bugs with 1 review pass. I almost didn't believe it. I was able to put it on a task (with dangerous permissions) and come back hours later to see it done, working, and clean.
I tried DeepSeek v4 and it wasn't able to make any meaningful progress at all. It kept creating dangling pointers and had trouble understanding the inline assempbly needed to be replaced if we were to compile for 64 bit. It kept getting stuck and looping on the same problem, without making progress.
What I do use DeepSeek for is lots of my automations on my websites. I find DeepSeek is fantastically cheap and fast and effective as summarization, collation, generating reports, finding and reporting issues from logs, etc. But I haven't found a way to get it to effectively port 90's C++ code to modern, cross-platform standards. But I want to be clear- I really like DeepSeek and use it wherever I can.. I mean.. it's so affordable!
I was building a cli tool that showed a graph of git commits, kind of like git log --graph, and deepseek v4 simply could not figure out a specific ui quirk where things weren't lining up correctly. I spent like $0.10 and 30 minutes trying to figure it out on deepseek.
Then I had deepseek summarize the bug, gave it to Opus, and it solved it in $1.12 and five minutes.
Fun fact, I was trying this afternoon Deepseek vs Opus 4.8 high, and I was surprised at how good Deepseek was. It outperformed Opus 4.8 on multiple occasions.
Found just later I was using v4 flash and not pro (for mistakenly setting the model to deepseek-chat and not v4-pro).
There are aspects about Deepseek I don't like though, when pushed against it will eagerly bend instead of reasoning and advocating for his points, something Opus 4.7 and later models started doing a lot (even when wrong).