DeepSeek recently officially raised its prices. As someone whose token usage was closing in on 100M tokens last quarter (see [My Token Usage Exploded 13× in Three Months]), I didn’t pay much attention at first — after all, DeepSeek was already very cheap, and even the raised price was still lower than the official price announced when V4 first launched. But I underestimated my usage: after a day of real-world testing at the new prices, it became clear that the cost is genuinely hard for an individual to bear. If I didn’t find a way around it, I’d be working just to pay for tokens.

I came across news about Lenovo’s new machine, the IdeaPad Vibe, these past few days. As someone who has been waiting for the Windows camp to respond since March or April, after reading through the coverage, all I can say is… come on, is that it?

I wanted to share files on my company’s Mac Mini with other Windows computers over SMB. The Mac clearly had “File Sharing” turned on, yet the Windows machines refused to see the machine, let alone the shared folders. After half a day of tinkering, I finally found the real culprit — with the help of a pile of command-line tools. This post records the whole troubleshooting process, and also gives a good rant about Windows’ junk-pile design that has only gotten messier from Win10 to Win11.

When I handed my workspace over to Multica back in May, I was happily picturing how letting AI take on more of the work would mean fewer late nights for me. The work did get done — but my token bill went through the roof. The other day I pulled a three-month usage report for the workspace out of curiosity, and I had to double-check that I was reading it right: about 38M tokens in May, jumping to nearly 500M in July, with a three-month total of 883M. So here’s a data-driven look at how my token consumption exploded over those three months — and why. Because my AI tasks have gone from “trying it out” to “can’t live without it”.

While setting up the Claude Science container, I learned about a new way of using NVIDIA GPUs inside containers, so I’m noting it down (most of it was written by AI, used as reference material for my own research).

The way I star GitHub repositories is pretty much the same as how I like and collect videos on bilibili: I just click them on a whim. Whenever I see a project that looks even remotely interesting, my brain always goes “might be useful someday” or “I’ll take a look later” — and my finger clicks the button before my brain finishes the thought.

That’s how, over the years, my star count quietly climbed past 800. To be honest, I have no idea what those 800+ projects actually are — most of them were starred because they seemed useful back then, and then never opened again.

I had already managed to get claude-science running in a container, and basic functionality worked without major issues. But when I wanted to do things like molecular docking, I couldn’t—the container simply had no GPU. However, when I pulled NVIDIA’s official image to build the container the same way I had before, something bizarre happened: every language kernel in CS—Python, Perl, R—stopped working, and the entire runtime environment was rendered useless.

This was truly beyond my understanding. After consulting Gemini manually with no luck, I decided to let opencode + deepseek-v4-flash handle it on its own—not me remotely typing commands and directing it, but an AI agent living inside the container that read the logs, bisected parameters, decompiled the parser, and edited the entrypoint itself. It was a strange and interesting experience; here’s a record of it.

Remember [that April post agonizing over device choices]? Back then I listed a bunch of candidates, weighed them one by one, and confidently declared I would “stick with the Fydetab Duo.” Well… it turns out humans can’t escape the universal law of zhen xiang (something you dismissed turns out to be great), and in the end I bought the MacBook Neo after all.

After previously tinkering with putting Claude Science into a Docker container, I’ve been using it relatively intensively over the past two weeks (connected to DeepSeek, not the original Anthropic version, of course), so I want to talk about its advantages and limitations.

I recently worked on a small project: putting the Linux version of Claude Science into a Docker container, paired with an API Bridge so it can run through third-party API backends without needing to hold an Anthropic API Key directly.

The process was more eventful than expected—also quite interesting. Here’s a record of it.