This kind of release shows Anthropic as a company is suffering from the same thing we all are right now. Removing the friction from having an idea and executing it stops you from remembering The Point. Yes, programming from your phone is an exciting modality and maybe even the future of how we work, but coding from your bedroom, AND the toilet, AND the woods AND your office is definitely (hopefully) not the future.
I wonder if is anyone working on an AI framework that encourages us to keep our eye on the big picture, then walk away when a reasonable amount of work is done for the day.
Yes, individuals are creating cool mobile coding solutions and Anthropic doesn't want to get left behind. I know I'm working my ass off at work right now because LLM coding makes it fun, but I also often don't prioritize what I'm doing for the big picture because I just try every thing that comes into my inbox, in order, because it's so fast to do with Claude Code.
There are two types of software engineers: Those who do and then think, or those who think and then do. Claude Code seems to strictly be for the former, while typically the engineers who can maintain software long-term are the latter.
Not sure if we have any LLM-tooling for the latter, seems to be more about how you use the tools we have available, but they're all pulling us to be "do first, think later" so unless you're careful, they'll just assume you want to do more and think less, hence all the vibeslop floating around.
> Claude Code seems to strictly be for the former, while typically the engineers who can maintain software long-term are the latter.
Given the number of CC users I know who spend significant time on creating/iterating designs and specs before moving to the coding phase, I can tell you, your assumption is wrong. Check how different people actually use it before projecting your views.
Yeah, I wasn't trying to say "These are the people who use CC, for these purposes" but rather what the intention seems to for Claude Code in the first place. I'm using CC from time to time, to keep up to date with what tooling is available, and also know people who use CC every day and plan a lot up front, sorry if I gave the impression that I meant that everyone using CC is doing that, was trying to get at what the purpose of the tool seems to be, which seems to be true today too, as the models continuously seem to steer you to "doing" and moving faster, not stopping and thinking.
This seems like a real coarse and not particularly accurate binary, but even if it were true, the thing about Claude Code and agentic coding like this is the cost of making a mistake or the cost of not being happy with a design and having to back it out is getting smaller and smaller.
I would argue that rapidly iterating reveals more about the problem, even for the most thoughtful of us. It's not like you check your own reasoning at the door when you just dive head first into something.
This isn't a binary thing - even if you prefer to build maintainable systems very often the trade-off is - you don't ship in time and there's no long term - the project gets scrapped.
So even if it comes at the expense of long term maintainability - everyone should have this in their toolbox.
I find it often helps me to see a feature before I evaluate if it was really a good idea in the first place. This is my failing--but one thing I like about Claude is that it's now possible to just try stuff and throw away whatever doesn't work out.
I usually have conversations with Claude for clearing my mind and forming the scope of a project. I usually use voice transcription from Claude app to take notes and explore all my options.
Same. When I can't be at my desk, my projects don't stop -- I just do the tasks that work well enough on the phone. Brainstorming, planning, etc. Or tasks that the agent can easily verify.
Having access to my local repository and my whole home folder is much easier than dealing with Claude or ChatGPT on the web. (Lots of manual markdown shuffling, passing in zipfiles of repositories, etc).
id say claude code is designed for think then do - thats where its different from other tools!
i think it still pulls to do then think because you cant tell what the agent understood of what you asked it to do from that first think, until its actually produced something.
I agree in your basic framing but not your conclusion. Met plenty of do-ers before thinkers that are self-aware enough to also maintain software longterm.
Claude Code and similar agents help me execute experiments, prototypes and full designs based on ideas that I have been refining in my head for years, but never had the time or resources to implement.
They also help get me past design paralysis driven by overthinking.
Perhaps the difference between acceleration and slop is the experience to know what to keep, what to throw away, and what to keep refining.
This is the real insight in this thread. The false binary of "rest OR work" is dissolving. I do some of my best problem-solving while walking my kid to school or making lunch...the context switch lets things percolate. Having a way to capture that momentum without needing to rush back to my desk and remember what I was thinking would be genuinely useful. The interface matters less than the latency between idea and execution.
"The false binary of "rest OR work" is dissolving."
If you're like most people in this forum, there are people who stand to gain financially if you convince yourself that you don't need boundaries between work and rest. You may even believe that you stand to gain financially, and that this will be best for you in the long term.
Please, take some time to rest for a day or two and really think about what you want your boundaries to be. Write them down.
> The false binary of "rest OR work" is dissolving
Sounds like someone hasn't yet worked multiple years with software engineering, or any job for that matter.
Your mind might trick you into believing it won't matter, but your body and mind NEEDS to be disconnected from work, 100%, at some point during your regular rhythms of life, otherwise you'll burn out much faster than the people you seemingly are trying to compete with.
Life never been a sprint, but it is a marathon, and if you spend all your young experience-less years on treating it as a sprint, you won't have any energy left for completing the marathon.
How is this not solved by a simple voice recorder? You can process and act on it later while not forgetting your thoughts when inspiration hits. People have been doing that for at least like 50 years now.
I’m guessing you’re suggesting it’s ok to lose time if you’re away from your computer enjoying life, and I agree. I also don’t see the issue in finding ways to be save time with work.
If you mean something different, please elaborate.
This kind of release shows Anthropic as a company is suffering from the same thing we all are right now. Removing the friction from having an idea and executing it stops you from remembering The Point. Yes, programming from your phone is an exciting modality and maybe even the future of how we work, but coding from your bedroom, AND the toilet, AND the woods AND your office is definitely (hopefully) not the future.
I wonder if is anyone working on an AI framework that encourages us to keep our eye on the big picture, then walk away when a reasonable amount of work is done for the day.
Yes, individuals are creating cool mobile coding solutions and Anthropic doesn't want to get left behind. I know I'm working my ass off at work right now because LLM coding makes it fun, but I also often don't prioritize what I'm doing for the big picture because I just try every thing that comes into my inbox, in order, because it's so fast to do with Claude Code.
We all sense it!: <https://newsroom.haas.berkeley.edu/ai-promised-to-free-up-wo...> <https://ghuntley.com/teleport/> <https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163>
There are two types of software engineers: Those who do and then think, or those who think and then do. Claude Code seems to strictly be for the former, while typically the engineers who can maintain software long-term are the latter.
Not sure if we have any LLM-tooling for the latter, seems to be more about how you use the tools we have available, but they're all pulling us to be "do first, think later" so unless you're careful, they'll just assume you want to do more and think less, hence all the vibeslop floating around.
> Claude Code seems to strictly be for the former, while typically the engineers who can maintain software long-term are the latter.
Given the number of CC users I know who spend significant time on creating/iterating designs and specs before moving to the coding phase, I can tell you, your assumption is wrong. Check how different people actually use it before projecting your views.
Yeah, I wasn't trying to say "These are the people who use CC, for these purposes" but rather what the intention seems to for Claude Code in the first place. I'm using CC from time to time, to keep up to date with what tooling is available, and also know people who use CC every day and plan a lot up front, sorry if I gave the impression that I meant that everyone using CC is doing that, was trying to get at what the purpose of the tool seems to be, which seems to be true today too, as the models continuously seem to steer you to "doing" and moving faster, not stopping and thinking.
This seems like a real coarse and not particularly accurate binary, but even if it were true, the thing about Claude Code and agentic coding like this is the cost of making a mistake or the cost of not being happy with a design and having to back it out is getting smaller and smaller.
I would argue that rapidly iterating reveals more about the problem, even for the most thoughtful of us. It's not like you check your own reasoning at the door when you just dive head first into something.
This isn't a binary thing - even if you prefer to build maintainable systems very often the trade-off is - you don't ship in time and there's no long term - the project gets scrapped.
So even if it comes at the expense of long term maintainability - everyone should have this in their toolbox.
I find it often helps me to see a feature before I evaluate if it was really a good idea in the first place. This is my failing--but one thing I like about Claude is that it's now possible to just try stuff and throw away whatever doesn't work out.
Was always possible. Now just easier.
1 reply →
I usually have conversations with Claude for clearing my mind and forming the scope of a project. I usually use voice transcription from Claude app to take notes and explore all my options.
Same. When I can't be at my desk, my projects don't stop -- I just do the tasks that work well enough on the phone. Brainstorming, planning, etc. Or tasks that the agent can easily verify.
Having access to my local repository and my whole home folder is much easier than dealing with Claude or ChatGPT on the web. (Lots of manual markdown shuffling, passing in zipfiles of repositories, etc).
id say claude code is designed for think then do - thats where its different from other tools!
i think it still pulls to do then think because you cant tell what the agent understood of what you asked it to do from that first think, until its actually produced something.
I agree in your basic framing but not your conclusion. Met plenty of do-ers before thinkers that are self-aware enough to also maintain software longterm.
I would definitely disagree.
Claude Code and similar agents help me execute experiments, prototypes and full designs based on ideas that I have been refining in my head for years, but never had the time or resources to implement.
They also help get me past design paralysis driven by overthinking.
Perhaps the difference between acceleration and slop is the experience to know what to keep, what to throw away, and what to keep refining.
These coding tools work better when you think and play first before doing...
One could just as easily argue hunching over your desk staring at your computer has neurological implications.
My favorite way to vibe code is by voice while in the hot tub. Rest AND focus AND build.
This is the real insight in this thread. The false binary of "rest OR work" is dissolving. I do some of my best problem-solving while walking my kid to school or making lunch...the context switch lets things percolate. Having a way to capture that momentum without needing to rush back to my desk and remember what I was thinking would be genuinely useful. The interface matters less than the latency between idea and execution.
"The false binary of "rest OR work" is dissolving."
If you're like most people in this forum, there are people who stand to gain financially if you convince yourself that you don't need boundaries between work and rest. You may even believe that you stand to gain financially, and that this will be best for you in the long term.
Please, take some time to rest for a day or two and really think about what you want your boundaries to be. Write them down.
1 reply →
> The false binary of "rest OR work" is dissolving
Sounds like someone hasn't yet worked multiple years with software engineering, or any job for that matter.
Your mind might trick you into believing it won't matter, but your body and mind NEEDS to be disconnected from work, 100%, at some point during your regular rhythms of life, otherwise you'll burn out much faster than the people you seemingly are trying to compete with.
Life never been a sprint, but it is a marathon, and if you spend all your young experience-less years on treating it as a sprint, you won't have any energy left for completing the marathon.
Take care of yourself, your mind and your body.
2 replies →
How is this not solved by a simple voice recorder? You can process and act on it later while not forgetting your thoughts when inspiration hits. People have been doing that for at least like 50 years now.
Wait why should I prefer being stuck in the office over taking a walk and periodically steering Claude code by phone?
On the other hand, you lose a lot of time if you step away from a session and it gets stuck asking for permission to do something simple.
Oh no! Anyway.
I don’t understand this comment?
I’m guessing you’re suggesting it’s ok to lose time if you’re away from your computer enjoying life, and I agree. I also don’t see the issue in finding ways to be save time with work.
If you mean something different, please elaborate.