Ask HN：如何戒掉 Claude 代码瘾？
3 分•作者: isomorph•29 天前
简而言之：我如何戒掉对 Claude Code 的工作狂式依赖？
各位 HN 用户，非常感谢你们阅读我的帖子。我想不到还有比这里更适合提出这个问题的社群了。如果这个问题也曾影响过你，我将非常感激你能在这篇帖子下留言。
我的目标：
作为一名专业的软件工程师，能够持续完成一天可接受的工作量，对当天修改的代码有合理的理解，大致准时下班，感觉自己做得足够了，并且能够将工作抛诸脑后，直到下一个工作日。
我的问题：
我发现随着工作日的进行和时间的流逝，我的编程风格逐渐偏离了 LLM 辅助编程（我负责设计和编写代码，只在遇到困难时才与 Claude Code 交流），而是越来越接近纯粹的“凭感觉编码”（Vibe-coding）。在这种模式下，我甚至不会去审查 Claude Code 生成的代码，直到积累了一大堆代码后，我才可能放弃它，除非它真的很有用，那样的话我会 painstaking 地审查它并尝试理解，通常需要进行大量修改才能达到我想要的效果——有时如果代码过于混乱或庞大，我仍然会放弃。这导致我在工作日结束后，花费数小时进行“凭感觉编码”。在 Claude Code 出现之前，我很少在没有外部压力的情况下工作到这么晚。这让我感到精疲力尽、沮丧，并且没有时间照顾自己和享受生活。
我之前的工作与生活平衡其实相当不错，所以近一年来的这种转变让我感到担忧。
我认为根本问题在于，“凭感觉编码”不像正常工作那样感觉“辛苦”，所以我可以一直做下去，但实际上我只是坐在电脑前工作，在工作日正式结束后很长一段时间里，我都无法参与到我的个人生活中。另一个因素是我目前拥有过多的自主权并且远程工作，这在以前还可以接受，但现在我和同事之间的沟通已经完全转向了与 Claude Code 的沟通。
我尝试过以下方法，取得了一些效果，但很难坚持，并且各有优缺点：
- 完全避免使用 Claude Code
- 自己手动输入它建议的修改，而不是让它直接修改（甚至复制粘贴）——这是我从 Frank King 博士那里学到的一个老技巧。这意味着我仍然需要花费精力进行逐字逐句的代码审查（可能无法完全“理解”它，但比仅仅看一眼然后批准/拒绝，或者更糟的是，进入“接受编辑”或“自动”模式要好）。之后我对代码感觉更安心。但到了工作日结束时，当我试图再挤出“一点点”功能时，我就会停止这样做。
- 只在“低”精力模式下使用 Claude，手动模式——审查（并与之争论……）每一个小的差异——这种方法有点用，但本身也很耗费精力。
- 设定一个硬性下班时间，无论我使用了多少 Claude Code。
- 提醒自己，我的工作不是尽可能快地完成整个项目——而是舒适地在工作日内尽我所能。
- 让 Claude 在工作日结束后告诉我停止（但它在长时间会话中会忘记这一点）。
- 将我的工作分成更小的块，这样我不得不中断它来提交 PR 并等待反馈，或者与同事讨论设计等。
我想，我的内在情绪状态、我的工作场所，以及我对自己生产力、目标以及 LLM 工具使用的自我叙述，都是导致这种行为的原因——当然还有其他因素。所以，关于工作狂/远程工作/居家办公的咨询和一般性建议可能会有帮助——如果你有任何想法，也欢迎提出。
非常感谢你的阅读，期待你的回复。
查看原文
TL;DR: How can I break my workaholic Claude Code addiction?<p>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.<p>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.<p>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.<p>My work-life balance before was actually pretty good, so the shift in the last year or so has alarmed me.<p>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.<p>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<p>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.<p>Many thanks for reading and I look forward to hearing from you.