Exploring ideas is a form of learning,
I'm not sure if I will look back on my life and think that I know too much and didn't produce enough widgets.
Addicted to Claude Code–Help
21–30 of 33 posts
Re: Addicted to Claude Code–Help
#22Without it you likely would have been in the same quagmire, but just slower?
It could have taken you years to realize that "oh I'm just exploring stuff and have no output".
Set an ambitious goal that is achievable using Claude Code, and focus on delivering it. Even if it doesn't turn out to be a hit, the experience of releasing it and using AI to accelerate it, will be a talking point to your 10-year-older self.
Re: Addicted to Claude Code–Help
#23Tokens per day
Re: Addicted to Claude Code–Help
#24I wish my other addictions were only $200/mo. Honestly. And for some, as satisfying as claude.
We're all in the same boat right now. Except for those who decry LLMs and loudly await the relevance of their artisanal coding skills to re-ascend. :)
Re: Addicted to Claude Code–Help
#25I know dozens of people who are in a similar state right now, following the November 2025 moment when Claude Code (and Codex) got really good . I wouldn't worry about it just yet - this is all very novel, and there's a lot of excitement involved in figuring out what it can do and trying different things. If you're still addicted to it in three months time I'd start to be concerned. For the moment though you're buildi…
I'm seeing the limits when Claude makes some statements that are extremely wrong but incredibly hard to spot unless you're in the field, recently telling me that "some people say" that rydberg atoms and neutral atoms are different enough to be in different quantum computing categories (they're the same). The stakes are lowering somehow, because I know I can't trust it for anything but fun side-projects. For serious research it's still me and reading papers.
Re: Addicted to Claude Code–Help
#26Listen, If you truly want help you've made the first step by realising what's wrong, but you won't get help here.
This community is obsessively pro-AI. Asking here is the equivalent of asking the guy who has sat at the slot machine next to you for the past three hours if he thinks you have a gambling problem. Of course he's going to say "no" or try to justify it, to do otherwise would be to admit to himself that he has a problem.
I don't have advice for you, other than to look up what gambling, drug, or alcohol addicts do. The path to recovery for all addiction is long and painful, but it can be done. Good luck.
Re: Addicted to Claude Code–Help
#27I know dozens of people who are in a similar state right now, following the November 2025 moment when Claude Code (and Codex) got really good . I wouldn't worry about it just yet - this is all very novel, and there's a lot of excitement involved in figuring out what it can do and trying different things. If you're still addicted to it in three months time I'd start to be concerned. For the moment though you're buildi…
Your mental model point is very true. We all had to learn how to google at some point — explaining how to use these tools to someone outside the bubble feels like explaining how googling works to someone. Much of it is intuitive understanding from experience. My question would be how much we think the processes will change as the models do. Much advice from two years ago is no longer relevant or realistic. Where do w…
> Much of it is intuitive understanding from experience.
You’re mistaking domain expertise with tool expertise. You can’t teach a non dev how to use an LLM effectively for dev without teaching them to be an experienced dev. Once you have that knowledge, LLMs aren’t that hard to use.
Re: Addicted to Claude Code–Help
#28I view Claude code same as how I used to use Jetbrains IDEs. I mean yes they are not same but even when I first learned of Pycharm pro and it's features I had this urge to make a lot of random idea apps. The landscape has changed but the solution is same. Prefer spending your time on things that give you long term happiness in any way.
The problem is it's not limited to code. I have Claude Code maintaining my Obsidian Vault, managing my Home Assistant setup via SSH, helping me buy life insurance and file my taxes and and manage my home orchard and...
Re: Addicted to Claude Code–Help
#29I view Claude code same as how I used to use Jetbrains IDEs. I mean yes they are not same but even when I first learned of Pycharm pro and it's features I had this urge to make a lot of random idea apps. The landscape has changed but the solution is same. Prefer spending your time on things that give you long term happiness in any way.
The problem is it's not limited to code. I have Claude Code maintaining my Obsidian Vault, managing my Home Assistant setup via SSH, helping me buy life insurance and file my taxes and and manage my home orchard and...
Unless you are buying life insurance and filing taxes daily this seems like a good thing.
Re: Addicted to Claude Code–Help
#30I know dozens of people who are in a similar state right now, following the November 2025 moment when Claude Code (and Codex) got really good . I wouldn't worry about it just yet - this is all very novel, and there's a lot of excitement involved in figuring out what it can do and trying different things. If you're still addicted to it in three months time I'd start to be concerned. For the moment though you're buildi…
I'm seeing the limits when Claude makes some statements that are extremely wrong but incredibly hard to spot unless you're in the field, recently telling me that "some people say" that rydberg atoms and neutral atoms are different enough to be in different quantum computing categories (they're the same). The stakes are lowering somehow, because I know I can't trust it for anything but fun side-projects. For serious r…
I'm not trying to convert you, just want to share process tips that I see working for me and others. We're using agents, not a chat, because they can do complex work in pursuit of a goal.
1. Make artifacts. If you're doing research into a tech, or a hypothesis, then fire off subagents to explore different parts of the problem space, each reporting back into a doc. Then another agent synthesizes the docs into a conclusion/report.
2. Require citations. "Use these trusted sources. Cite trusted sources for each claim. Cite with enough context that it's clear your citations supports the claim, and refuse to cite if the citation doesn't support the claim."
3. Review. This lets you then fire off a subagent to review the synthesis. It can have its own prompt: look for confirming and disconfirming evidence, don't trust uncited claims. If you find it making conflation mistakes, figure out at what stage and why, and adjust your process to get in front of them.
4. Manage your context. LLM only has a fixed context size ("chat length") and facts & instructions at the front of that tend to be better hewn to than things at the end. Subagents are a way of managing that context to get more from a single run. Artifacts like notebooks or records of subagent output move content outside the context so you can pick up in a new session ("chat") and continue the work.
It's less fun that just having a chat with ChatGPT. I find that I get much better quality results using these techniques. Hope this helps! If you're not interested in doing this (too much like work, and you already have something that works), it's no skin off my nose. All the best!