Ask HN：如何摆脱对 Claude Code 的工作成瘾？

**简而言之：**我该如何摆脱对 Claude Code 的工作狂式依赖？

各位 HN 用户，真心感谢你们阅读这篇帖子。我想不出还有比这里更适合提出这个问题的地方了。如果这个问题曾以任何形式影响过你，我会非常感谢你能在这篇帖子下留言。

**我的目标：**能够作为一名专业软件工程师，稳定地完成可接受的一天工作；对当天修改过的代码部分保持相当不错的理解；大致按时结束一天的工作；感觉自己做得够多了；并且觉得可以把工作放下，直到下一个工作日再去想它。

**我的问题：**随着工作日不断推进、剩余时间越来越少，我的编程方式会越来越偏离 LLM 辅助编程（由我设计和编写代码，只在卡住时才与 Claude Code 交流），而越来越接近纯粹的氛围编程（vibe coding）：我甚至不会审查它写出的代码，直到积累起一大块内容；届时我很可能会直接放弃它。除非它确实很有用，在这种情况下，我会费力地审查并尝试理解它，而且通常还得做很多修改，才能让它变成我想要的样子——如果它太混乱或规模太大，有时我仍然不得不放弃它。

这导致我在工作日的晚上、正式下班之后，花费数小时进行氛围编程。在 Claude Code 出现之前，我很少会在没有外部压力的情况下工作到那么晚。这让我感到精疲力竭、沮丧，也减少了我照顾自己和过自己生活的时间。

我以前的工作与生活平衡其实相当不错，所以过去一年左右发生的这种转变让我感到警惕。

我认为根本问题在于，氛围编程在主观感受上不像“辛苦的工作”，因此我可以不断继续做下去；但本质上，我只是在正式工作日结束很久之后，依然坐在电脑前工作，而没有参与自己的个人生活。另一个因素是，我目前拥有过多自主权，而且是远程办公；以前这没有问题，但现在我与同事之间的沟通，已经在很大程度上被我与 Claude Code 的沟通所取代。

我尝试过以下方法，并取得了一些效果，但它们都很难坚持，而且各自有优缺点：

• 完全不使用 Claude Code。
• 始终亲自输入它建议的修改，而不是让它直接执行修改（甚至不复制粘贴）——这是我从 Frank King 博士那里学到的一个老办法。这意味着我仍会付出逐字符审查代码的努力（也许并不代表我完全“理解”了它，但仍然比只是眯着眼看一眼再决定批准/拒绝要更接近理解；更糟糕的情况则是进入“接受修改”或“自动”模式）。而且之后我会对这些代码感觉更安心。但在一天快结束、试图再挤进“一点点功能”时，我就会停止这样做。
• 只以 Claude 的“低”投入模式、手动模式使用它——审查（并与之争论……）每一个小 diff。这种方式多少有效，但也会以另一种方式让人疲惫。
• 无论使用 Claude Code 的程度如何，都设定一个必须结束工作日的硬性截止时间。
• 提醒自己：我的工作并不是以最快速度完成整个项目，而是在一个工作日内尽可能舒适地完成自己能做的事情。
• 告诉 Claude，在工作日结束后提醒我停下来（不过它会在长会话中忘记这一点）。
• 将工作拆分为更小的部分，使我必须中断工作来提交 PR、等待反馈，或与同事讨论设计等。

我想，我内在的情绪状态、我的工作环境，以及我对生产力、目标和 LLM 工具使用方式所讲述的那些故事——还有其他因素——共同造成了这种行为。因此，关于工作狂、远程办公或居家办公（WFH）的心理咨询和一般建议或许也会有所帮助；如果你对此有任何想法，也非常欢迎。

非常感谢你的阅读，期待听到大家的看法。

TL;DR: How can I break my workaholic Claude Code addiction?

Hello HN users, I really appreciate you reading this. I can't think of a better audience for this question. If this issue has affected you in any way, I would be really thankful to you if you could leave a comment on this post.

MY GOAL: to be able to consistently do an acceptable day's work as a professional software engineer, keeping a reasonably good understanding of the parts of the code that I changed that day, ending the day roughly on time, feeling like I did enough, feeling like I can forget about work until the next workday.

MY PROBLEM: I find that as the workday goes on and time runs out, my style of programming gets further from LLM-assisted coding (me designing and writing code, talking to Claude Code only when I get stuck) and closer to pure vibe-coding (where I don't even review the code it writes until a big chunk has built up at which point I'm likely to abandon it, unless it's really useful in which case I'll painstakingly review it and try to understand it and usually have to make a lot of changes to get it how I want it - sometimes I'll still have to abandon it if it's too confusing or large). This leads to me spending hours and hours on vibe-coding sessions on workday evenings, after the workday is over. In the pre-Claude-Code era, working that late (with no external pressure) was much rarer for me. This leaves me feeling drained, frustrated, and with less time to look after myself and live my life.

My work-life balance before was actually pretty good, so the shift in the last year or so has alarmed me.

I think the fundamental problem is that vibe coding doesn't feel as "hard" as work, so I can just keep doing, but essentially I'm just sitting at the computer working and not participating in my personal life long after the workday is officially over. Another factor is that I have too much autonomy at the moment and work remotely, which was OK before but now the communication between myself and colleagues has been really redirected into communication with Claude Code.

I've tried the following with a bit of success but they're hard to stick to and all have their own pros and cons: - Abstain from using Claude Code at all - Always typing out the edits it suggests myself instead of letting it make them (or even copy-and-pasting) - an old trick I learned from Dr Frank King. This means I keep the effort of doing a certain kind of character-by-character code review (maybe not "understanding" it fully but still getting closer than if I just squint at it and approve/deny, or worse, go into "accept edits" or "auto" mode). And I feel more comfortable with the code later. But I just stop doing this at the end of the day when I'm trying to squeeze in "one more bit" of functionality - Only using claude in "low" effort mode, manual mode - reviewing (and quarreling with...) every little diff - kind of works but feels draining in its own way - Setting a hard deadline to end the workday, regardless of how much Claude Code I'm using. - Reminding myself that my job isn't to complete the whole project as fast as possible - it's to do as much as I can (comfortably) in a workday - Telling Claude to tell me to stop after the workday is over (it forgets this in long sessions though) - Splitting my work into smaller chunks so that I have to interrupt it to make PRs and wait for feedback, or discuss design with colleagues etc

I guess my internal emotional state, my workplace, and the stories I tell myself about my productivity, my goals, and the use of LLM tools, are all responsible for this behaviour - among other things. So counselling and general advice about workaholism / remote working / WFH would probably help - that's welcome too if you have any thoughts.

Many thanks for reading and I look forward to hearing from you.