How to break Claude Code addiction?

Join the discussion

• Hacker News
• go outside
  by moomoo11
• "this is a well-structured prompt. i'll pull up the relevant research and return with suggestions."
  by chessucation
• What's your point - that I've written this post as if it's a prompt? (Probably true...)
  by isomorph
• Start interviewing for jobs and tell them exactly what you want and how you want to work.
  by paulcole
• If you've played video games you're familiar with the dopamine hit you get when defeating a big boss, solving some hard puzzle or finding rare loot. In some ways, solving problems with software is the same way. Its the same feeling and using AI in the last 6+ months has accelerated the pace at which you can get those dopamine hits.

  That feeling is what's addictive. To use the video game analogy, if you could skip the grindy elements of repeating a boss fight over and over and just get more chances at the rare loot you probably would. Some call this a cheese, the community finds a cheesy way to defeat the boss easily so you do that and its a 5 min fight vs. 30. That's what AI is helping with: the grindy elements of coding.

  I think you can still reach burnout (both in games and software) even if the grindy parts are getting automated. You can certainly ignore AI and hand code but statistically speaking you will probably be "left behind" from your peers.

  Does your employer incentivize contributions individually and can you advance with this pace of work? If there are financial incentives it might make sense to put in extra effort. If your employer is in more of "its a marathon, not a sprint" mode and your contributions are to the greater good then put down the work at the end of the day and find something else to do. Set aside AI and ask yourself if its worth it putting in 2 extra hours per day.

  by mattbrewsbytes
• I probably would try to delegate to Claude or any other agent quite long and hard task and then log off for the day living my offline life. Thus definitely remove my "guilt" for not being productive and let the useful work being produced. Not ideal,I know, but this is what I was doing lately
  by tazumi
• If you could that reliably, you wouldn’t have a job
  by figassis
• Sounds good but then I end up inspecting the output, restarting a session
  by isomorph
• I'm in a similar situation.

  Programming used to be painful, but coding with AI doesn't feel that way. In the old days, I had to write extensive planning documents before writing any code—work orders, UI layouts, and design specs. With AI, things happen right away. I think the immediate feedback is a huge difference.

  To keep my skills from deteriorating, I avoid using AI when reviewing other people's work. I end up missing AI.

  by jdw64
• Interesting thanks. I always find code review (even of my own code) pretty difficult, and I think in this LLM coding era, I've been avoiding it as much as possible. Maybe if I lean in to it, it'll close the pleasure gap between vibe coding and "normal" or "merely AI-assisted" coding and I'll be able to get a handle on it
  by isomorph
• Okay, I think the first problem is calling it an addiction because it is a similar feeling if you want to keep coding in machine code instead of moving higher in the hierarchy and start working with C++. It is an extremely handy tool to be able to produce some work, so you shouldn't take it off your belt. However, I will talk about Gemini addiction, where I can't even decide which color of shoes I should buy. I'm asking it to pick for me, which is terrible. So there is that.
  by poxlr
• Interesting points, thank you. To explore your idea: what if I was addicted to using C++? I don't mind using the new, high-level tool all day (be it Claude Code or C++), but it's continuing to vibe code with it for several hours AFTER the workday is OVER that is bad. To your point, I guess when one learns a more powerful programming language, there is an initial period of enthusiasm and then it might wear off and become more mundane. Maybe I just haven't reached that with Claude Code yet. It feels like Claude Code has kept improving quickly, which may have kept this workaholic binge cycle going for longer than usual. Regarding the non-code decision stuff - yes, it's definitely related. I have always been someone who researches, seeks reassurance, and wants expertise and rules to apply to my decisions, instead of making them from the gut. I suppose this "Ask HN" post is an example of that, in a way - I'm crowdsourcing solutions to a personal problem. But it feels different (and better) to seek opinions from human beings - even though they will be represented to me as text, just like "opinion-like" strings of words from Claude... when I was younger I would describe myself as addicted to online forums. So I guess the artificiality of the intelligence isn't the problem. It's just the speed and always-on connectedness - similar to the internet itself.
  by isomorph
• Pure vibe-coding isn’t that satisfying (as you’ve discovered) the problem is you’re constantly reviewing its huge output, and it probably goes wild in directions making assumptions.

  It’s much more fulfilling to give the LLM guardrails by engineering the solution.

  This means coming up with the high level architecture, dependencies, breaking down the system into deliverable chunks, and implementing those chunks. The LLM can help in all those steps of the process. And it will be much easier to review and keep an understanding of the code.

  by gitgud
• Personally, I only have success with coding agents if it's for filling in some design I already engineered and half-implemented (like added interfaces and method declarations for example)

  I feel like this is the best way to condition the agent, I don't have much success trying to do it via the prompt only

  by LelouBil
• Clear the session after 300k tokens and force your workflow to adapt to it. The rabbit holes come when you’re at context rot and blindly following Claude debugging some problem that you shouldn’t even be trying to solve.

  Other than that, set an alarm when you want to stop working. When it rings, physically unplug your work laptop and move it somewhere out of sight.

  by chatmasta
• Thank you for the actionable suggestions. I will try them both.
  by isomorph
• I know this feeling. Before AI you had to evaluate an idea, plan its inplementation, judge if it is worth it or even doable. Now, you just prompt and see if you keep the output and think of the next thing to do. This can feel addictive. When i get lost in this i try to step away and think about what the bigger goal is and whether i am just distracting myself. I guess this helps me not get drained. But there is something which also helps tremendously: my coworkers do not work on the same things as i do. if they did, i would feel a big pressure to finish first. Are you competing with anyone?
  by HellDunkel
• Vibe coding is addictive for the same reasons slot machines are.

  Sometimes the output is great, sometimes not, but it always feels like a change to the prompt will get you closer to the prize. Just like pulling the handle on a slot machine gets you one more chance at a jackpot.

  by ungreased0675
• Today I opened Twitter. I had 1.5K followers back in the day. I think it had similar dynamics: an immensely powerful tool, but users had no discipline and those running it had really bad incentives.
  by gritzko
• Is this work related or addiction related? You are repeatedly pulling a slot machine in hopes for a jackpot of working usable code, something which does not come up just often enough to require another pull of the conversation turn.

  Claude does not have a sense of time. What is stopping you from not talking to it until the next day?

  by kay_o
• I think you're right that it's not that really "work" related. What's stopping me is that I don't want to give up the chance of another little "hit" from it. I suppose that mechanism is a big part of why I enjoy coding in the first place, which might explain why it's difficult to disentangle what I like about my job from the addictive nature of vibe coding.
  by isomorph