DEV Community

hummingbirdLabs
hummingbirdLabs

Posted on • Originally published at hummingbirdlabs.github.io on

Deepseek V4 Pro Price Drop Again on May 23, 2026

Worried about Deepseek returning to full price in June 2026, but unexpectedly it dropped again yesterday

Here’s the information from Deepseek’s official website: For all models, the input cache hit price has been reduced to 1/10 of the launch price. This price adjustment takes effect from 2026/4/26 12:15 UTC.

The deepseek-v4-pro model API pricing will be officially adjusted to 1/4 of the original price after the 75% discount promotion ends on 2026/05/31 15:59 UTC. Figure 1

This means: Deepseek V4 Pro will permanently stay at 25% of the original price.

DeepSeek is so generous, I must support them by adding funds. So I happily recharged another 700 RMB (about $100 USD) to DeepSeek. Let’s see how long this $100 credit will last. Figure 1

Model capabilities still need improvement. Fixing certain UI interaction bugs isn’t necessarily faster than human developers.

I’ve found that on Windows WPF UI, all models (deepseek-v4-pro, Qwen3.6 Plus, Claude Sonnet 4.6, etc.) don’t perform very well. They easily produce compilation errors, runtime errors, and various UI data passing anomalies.

Is it because the Windows tech stack has fewer training materials for models, plus the numerous and complex library versions, leading to poor model performance?

My current solution is: add detailed local logs in debug mode to provide AI with more runtime information.

Static code + runtime logs = complete program information.

Simply letting the LLM review code is not enough. Because the LLM can only judge program behavior based on static code. There are many hidden assumptions here. When AI reviews only a portion of code, it assumes other modules are working correctly.

If you let AI review all code in a project, the context becomes too long, leading to AI hallucinations (I mentioned this in a previous blog).

So I strongly recommend: always add detailed local logs in debug mode to provide AI with more runtime information.

A Brief About Me

I’ve worked at NetEase Games, Baidu, Tencent (8 years), and Meituan (nearly 7 years), leading large-scale R&D projects and managing teams of 100+ engineers.

Currently, I’m pursuing entrepreneurship in the AI field.

Why? The world runs on uncertainty — staying in corporate roles too long breeds addiction to certainty. Starting an AI venture is like setting sail into uncharted waters.

Feel free to reach out: mailto:HummingbirdLabs@outlook.com.

Top comments (0)