Unless you have the source for the latter it's nothing more than propaganda. Also, DeepSeek report is 2-3 years old, and at that time there were no huawei chips, at least not known to the public. This is a different model, in different age where huawei chips are already delivered into the production as we see
Why do you think the Chinese are not using their ai chips, which afaics are from huawei, to train their models? If that is true, which I think it is, we don't have to wait until 2030 to see if they're gonna match the performance of nvidia GPU. The evidence is already here - glm is among the most competitive models out there.
> Compared with our initial baseline on the same hardware, we achieved a 3× improvement in end-to-end serving performance, reaching hardware efficiency and per-token cost comparable to mainstream NVIDIA GPUs. This demonstrates that Chinese chips can support frontier-model inference efficiently and economically at scale.
Sometimes the winters may be cold, some other times they may be exceptionally warm, and sometimes they're a mix of both. The law remains the same regardless what the winter was or is like. Countries that have exceptionally warm winters do not really have a winter conditions so I'd guess their law wouldn't have a requirement for winter tires or chains
I started using gemini with caution given the "much worse" benchmarking points it has gotten and still does but in practice there's very little evidence I found in comparison to claude models. It performs really well on non trivial tasks.
You're correct, the difference isn't nil - H100 is data-center grade GPU with loads of bandwidth and compute while RTX PRO is a consumer grade GPU. The difference between the microarchitectures would make sense to point out if we had been comparing apples to apples and not apples to pits.
Worktrees are significantly faster to use and checkout than clones. They also use much less disk space, and obviously commits made in one worktree do not require git plumbing to get them visible in another etc.
If I strip the dependencies out, I'm using it on a 5MLoC C++ codebase, and I found it performs really really well. I am using the Opus 5/Fable in parallel and I couldn't tell the difference. Both models make mistakes here and there.
I don't see how useful this benchmark at all is for tracking the progression of models. I am not intending to bash on you personally but this is useless. People who are using AI models everyday are for sure not interested how close the AI model can visualize the pelican but they are interested in how they will perform on their daily tasks at work or private use. Correlation between doing good on pelican task and doing good on actual work you need to do is close to zero.
Mechanics I've been to generally have no idea about how things actually in the car work - from what I could understand, area is full of recurring problems, and this exactly benefits mechanics to solve them through trial and error approach rather than understanding much how underlying things work. Pretty much close to what I would say SWE will turn into, there's no other choice IMO in foreseeable future.
Software by definition has always been and will remain broken in one or another way. AI makes no difference or whatsoever. Arguably, it will help raising the quality of software.
Evidence so far does not suggest people driving off a cliff so while a valid concern it's not a likely one. We also acknowledged that the benefit of using a vehicle is such that it outnumbers the risks it may introduce. We never said there will be no risks attached.
When the combustion engine was invented, and we got the means by which we could accelerate our trip by 10x, and at the same time scale it to multiple people, we didn't tell the humans to keep pushing the vehicles by their hands, didn't we?
Exactly. That would mean going back to square one, and I also personally don't review the code anymore but I am more focused on asking the model to demonstrate the value it created through benchmarks, workload-generators, and e2e tests.
Mostly it proves as a valid approach, barring the bugs the model can introduce to value-demonstrating benchmarks which can of course skew the evidence on hypotheses, and thus code trajectory the model opts to go with.
The problem I see with this is really that I am not anymore under the control but I am not sure I see other alternative. I am becoming more and more like a system observer with surface-level understanding of the system rather than the engineer with zoomed-in level of understanding of how the code actually behaves. Perhaps we're transitioning into a QA roles present.
Assuming you're investing aggressively and not touching that money for the next 20 years, with the nominal return of 6% per year, adjusted for the inflation rate of 3% per year, 1M will increase to 1.8M. Not sure how you came up with 8M.