Day 047: Cutting Dependency at the Root — Builder's Log

A platform lockout turned into a live resilience test today. We removed a core dependency, kept the stack shipping, and learned again that control matters more than convenience.今天一次平台封禁，反而变成了一场真实的系统韧性测试。我们拔掉一个核心依赖，主链路照样继续产出，也再次确认了控制权比便利更重要。

Lost access to a tool I had leaned on for a long time, then used the shock to test what in the stack was actually mine.
Removed Claude Code, Claude Desktop, and the leftover Claude apps from the Mac mini instead of pretending a half-broken dependency was still part of the system.
Cleaned up the US event-driven workflow by stripping out untrusted web price pulls and letting the price layer stay with the data path built for that job.
A Google token issue was still sitting there tonight, which was a good reminder that “production” is not the same thing as “actually working.”
I liked the clarity of the day. When a platform can pull the plug whenever it wants, the real question is not how to beg for access back, but what capabilities should live on infrastructure I control.
Family life stayed in the frame too: a day trip, train time with learning, and a quiet reminder that a system is only worth building if it leaves room for real life.
Ended the day with fewer moving parts, less illusion, and a stronger bias toward tools that can disappear without taking the whole workflow down.

一个我用了很久的工具突然失去访问权限，今天反而逼着我认真看清，系统里到底哪些东西是真正属于自己的。
没有假装这层依赖还能凑合用下去，而是直接把 Mac mini 上的 Claude Code、Claude Desktop 和残留 Claude app 一次性清掉。
美股事件驱动那条链路也顺手收干净了，把不可信的网页价格抓取拿掉，让价格继续留在更靠谱的数据路径里。
今晚 Google token 还是报错，这事也再次提醒我，“已经发布 production”不等于“现在真的能用”。
我挺喜欢今天这种清醒感。平台随时能收回入口时，真正该想的不是怎么把权限求回来，而是什么能力必须沉到底层，放在自己能控制的地方。
生活那条线也没有被系统吞掉，白天出行，高铁上陪着学习，反而让我更确定，工具做得再强，也该给真实生活让路。
一天结束下来，系统零件更少了，幻觉更少了，我也更偏向那些就算某个工具明天消失，整套工作流还是能继续往前走的东西。

Day 047: Cutting Dependency at the RootDay 047：从根上砍掉依赖