Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: How to break Claude Code addiction?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 36 posts

Re: Ask HN: How to break Claude Code addiction?

#11

Post by gitgud »

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.

Re: Ask HN: How to break Claude Code addiction?

#14

Post by chatmasta »

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.

Re: Ask HN: How to break Claude Code addiction?

#15

Post by jdw64 »

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.

Re: Ask HN: How to break Claude Code addiction?

#19

Post by isomorph »

kay_o wrote: post #2

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?

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.

Re: Ask HN: How to break Claude Code addiction?

#20

Post by isomorph »

chatmasta wrote: post #14

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.

Thank you for the actionable suggestions. I will try them both.
Post reply on HN