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>
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.
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.
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.
So even if it comes at the expense of long term maintainability - everyone should have this in their toolbox.
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).
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.
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.
My favorite way to vibe code is by voice while in the hot tub. Rest AND focus AND build.
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.
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.
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.