Another new week has arrived. This morning, I took Q to the subway station. Since the road we took before is still under construction and the many soil-hauling trucks were kicking up clouds of dust, we took another route today and discovered a whole new world. It turns out I can take the main road outside directly to the office—a long, straight road with a non-motorized lane, too. I’ll just have to take it for a few more days to see whether there are any traffic police around.

The original plan for the morning was to work on the app first, but right after finishing breakfast, I received a new assignment. More new work? This time it’s a Shopify standalone store. Although I had heard of it before, I had never used this cross-border e-commerce platform. It feels like I get to work with new things every day at this new company, though there’s a bit too much to handle.

The boss’s idea was probably to set up a Shopify standalone store for each sub-brand. I looked into it and found that it’s a closed-source SaaS system that can’t be deployed on your own server; you can only host it on the Shopify platform, which leaves very little room to tinker. While waiting for my operations colleague to register an email address, I continued working on the app that I hadn’t finished last week. Today, I brought an Android phone specifically to use as a debugging device.

In the afternoon, everything fell apart. I discovered in VS Code that Claude Opus 4.6 had disappeared again, replaced by the Free Auto mode. I immediately went to Xianyu to confront the seller, only to be told that Github was causing trouble. Ever since Github changed the benefits of its student package a few days ago, it has once again begun broadly restricting abuse scenarios such as reverse proxies. I was just honestly using Copilot and got caught in the crossfire too.

Fortunately, the Github account wasn’t ruined and I can open another one. Otherwise, I would have lost my capable assistant forever. With the powerful Opus’s help, development progressed fairly smoothly in the afternoon. The only thing that got stuck was React Navite crashing frequently in BLE scenarios. Opus and I spent a long time debugging it, and finally traced the problem to an upstream dependency library.

Opus’s solution was to apply a patch. I thought I’d check whether this upstream dependency library had been updated, and it turned out that it had—and the issue had already been fixed. I’ve learned my lesson this time: when I encounter a similar situation again, I’ll first check whether the dependency has been updated.