61–67 of 67 posts
This looks absolutely wonderful. Is it possible to run against Claude remotely (e.g. on a VM?). Or should I ask Claude to add that?
Ask Claude ;) Right now it is hard-coded to run `claude --resume ` but there's a natural abstraction to use a different script to start the Claude session. If you're being sarcastic, I love you anyways.
This advice will be very dated when inference gets an order of magnitude faster. And it will happen—it’s classic tech. Probably will even follow moores law or something. Wait until that 8 minute inference is only a handful of seconds and that is when things get real wild and crazy. Because if the time inference takes isn’t a bottleneck… then iteration is cheap.
Yea, I think it will be totally useless to switch at that level and instead it will be about reviewing the work more effectively. I think I would believe in the more "autonomous Claude" systems in that world.
(Presumably cost per token will be dramatically lower as well)
Earlier quoted context omitted.
There's also a concern I don't hear folks talk about: the potential for all of this multi-tasking to be causing issues in your wellbeing or even harming your brain. Eg: "For example, functional magnetic resonance imaging (fMRI) studies have shown that multitasking reduces activation in brain regions involved with cognitive control while increasing activation in areas associated with stress and arousal" - from https:/…
I tried running multiple agents concurrently, but it is exhausting. My brain feels completely murdered and unhappy at the end of the day. I can do two, and keep both contexts active in my head, but not more than that. And even that feels stressful.
Earlier quoted context omitted.
There's a lot more "telling" than "showing" going on. By that I mean - the people claiming hyper-productivity from their GasTown setup never have actual products to demo.
So far the only company that is really outspoken about the scale of their vibe coding has been Anthropic. However their uptime and bug count is atrocious.
If you are letting Claude run for seven minutes at a time, you aren't thinking hard enough about what you're building. If you start trying to juggle multiple agents, you are doubling down on the wrong strategy. https://hbr.org/2010/12/you-cant-multi-task-so-stop-tr
The rest of my time goes to prepping those big features (designing, speccing, talking, thinking, walking).
Going to see how big a feature can be before the quality suffers too much and it becomes unmaintainable. This highly depends on how good I spec it out and how good I orchestrate the agentic workflow.
Earlier quoted context omitted.
I can do two or three at a time. I treat them a bit like queues: Last in first out, sort of like we do with our human peers. We delegate work, we tend to some other work, and we code review much later in the day. The secret to this mindset is that it doesn't always have to line up. Let your agent wait for you; You'll get to their output next.
I don’t know about you but I’m not constantly round robin delegating work to peers and reviewing it on a 10-20 minute cadence. No one works like that. I don’t know if anyone is even capable of working like that day in and day out long term for any meaningful definition of review.
Sometimes yes, but often no. It takes time to write what you need into claude code and to review what it makes.
I do whatever work I need to do, however long it takes, send to claude, and immediately pop off the next queue item.
Earlier quoted context omitted.
I don’t know about you but I’m not constantly round robin delegating work to peers and reviewing it on a 10-20 minute cadence. No one works like that. I don’t know if anyone is even capable of working like that day in and day out long term for any meaningful definition of review.
Who said a 10-20 minute cadence? :) Sometimes yes, but often no. It takes time to write what you need into claude code and to review what it makes. I do whatever work I need to do, however long it takes, send to claude, and immediately pop off the next queue item.
Micromanaging 3 junior engineers working on different tasks to the point where you are reviewing each one’s work multiple times per day and assigning new tasks multiple times per day sounds like a quick ticket to burnout.