问HN:如何摆脱对Claude Code的依赖?

3 分•作者: isomorph•30 天前•原帖
TL;DR:我该如何摆脱对工作狂Claude Code的依赖? <p>大家好,感谢你们阅读这篇文章。我觉得你们是问这个问题的最佳听众。如果这个问题对你有任何影响,我将非常感激你能在这篇帖子下留言。 <p>我的目标: 作为一名专业软件工程师,我希望能够稳定地完成一天的工作,保持对当天所修改代码部分的合理理解,准时结束工作,感觉自己做得足够,并且能够在下一个工作日之前忘记工作。 <p>我的问题: 我发现随着工作日的进行,时间的流逝,我的编程风格越来越远离LLM辅助编码(我自己设计和编写代码,只有在遇到困难时才与Claude Code交流),而更接近于纯粹的“随意编码”(在这种情况下,我甚至不会在一大段代码生成之前审查它,等到代码堆积到一定程度时,我可能会放弃,除非它真的有用,否则我会费力地审查并试图理解,通常需要做很多修改才能达到我的要求——有时如果代码太混乱或太大,我仍然会放弃)。这导致我在工作日的晚上花费数小时进行随意编码,工作结束后仍然在电脑前忙碌。在Claude Code出现之前,我很少会在没有外部压力的情况下工作到那么晚。这让我感到精疲力竭、沮丧,并且没有足够的时间照顾自己和生活。 <p>我之前的工作与生活平衡其实相当不错,因此过去一年左右的变化让我感到震惊。 <p>我认为根本问题在于,随意编码并没有让我感到“艰难”,所以我可以一直继续,但实际上我只是坐在电脑前工作,工作日结束后很久都没有参与我的个人生活。另一个因素是我目前拥有过多的自主权,并且远程工作,这在之前是可以的,但现在我与同事之间的沟通实际上被转向了与Claude Code的沟通。 <p>我尝试过以下方法,取得了一些成功,但都很难坚持,并且各有优缺点: - 完全不使用Claude Code - 自己手动输入它建议的修改,而不是让它自动修改(或者甚至复制粘贴)——这是我从Frank King博士那里学到的一个老技巧。这意味着我保持对某种逐字逐句代码审查的努力(也许不能完全“理解”,但比我只是眯着眼睛批准/拒绝要接近得多,或者更糟的是,进入“接受修改”或“自动”模式)。这样我对代码的理解会更深。但在一天结束时,当我试图再挤出“最后一小部分”功能时,我就会停止这样做。 - 只在“低”努力模式下使用Claude,手动模式——审查(并与之争论……)每一个小的差异——这种方法有点有效,但以自己的方式让人感到疲惫。 - 设置一个严格的截止时间来结束工作日,无论我使用多少Claude Code。 - 提醒自己,我的工作不是尽快完成整个项目,而是在工作日内尽可能多地(舒适地)完成工作。 - 告诉Claude在工作日结束后提醒我停止(不过它在长时间的会话中会忘记这一点)。 - 将我的工作分成更小的部分,这样我就必须中断工作以进行PR并等待反馈,或者与同事讨论设计等。 <p>我想我的内心情绪状态、工作环境,以及我对自己生产力、目标和使用LLM工具的故事,都是导致这种行为的原因之一。因此,关于工作狂、远程工作和居家办公的咨询和建议可能会有所帮助——如果你有任何想法,我也非常欢迎。 <p>非常感谢你的阅读,期待你的回复。
查看原文
TL;DR: How can I break my workaholic Claude Code addiction?<p>Hello HN users, I really appreciate you reading this. I can&#x27;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&#x27;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&#x27;t even review the code it writes until a big chunk has built up at which point I&#x27;m likely to abandon it, unless it&#x27;s really useful in which case I&#x27;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&#x27;ll still have to abandon it if it&#x27;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&#x27;t feel as &quot;hard&quot; as work, so I can just keep doing, but essentially I&#x27;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&#x27;ve tried the following with a bit of success but they&#x27;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 &quot;understanding&quot; it fully but still getting closer than if I just squint at it and approve&#x2F;deny, or worse, go into &quot;accept edits&quot; or &quot;auto&quot; mode). And I feel more comfortable with the code later. But I just stop doing this at the end of the day when I&#x27;m trying to squeeze in &quot;one more bit&quot; of functionality - Only using claude in &quot;low&quot; 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&#x27;m using. - Reminding myself that my job isn&#x27;t to complete the whole project as fast as possible - it&#x27;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 &#x2F; remote working &#x2F; WFH would probably help - that&#x27;s welcome too if you have any thoughts.<p>Many thanks for reading and I look forward to hearing from you.