Wtf is this LLM slop
Don't Wait for Claude
21–30 of 67 posts
Re: Don't Wait for Claude
#22When computer works, it's sword fighting time. I don't make the rules
I'm not slacking off, Claude is shmorgalizing.
Re: Don't Wait for Claude
#23> The fix is obvious: work on something else while Claude runs.
Disagree. The fix is actually counter-intuitive: give Claude smaller tasks so that it completes them in less time and you remain in the driver's seat.
Re: Don't Wait for Claude
#24If 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
Why should Claude finish complex tasks in less than seven minutes?
Computers are fast. If a physic engine can compute a game world in 1/60 of a second. The majority of the tasks should be done in less than 7 minutes.
Whenever I see transcript of a long running task, I see a lot of drifting of the agent due to not having any context (or the codebase is not organized) and it trying various way to gather information. Then it settle on the wrong info and produce bad results.
Greppability of the codebase helps. So do following patterns and good naming. A quick overview of the codebase and convention description also shortens the reflection steps. Adding helper tools (scripts) help too.
Re: Don't Wait for Claude
#25Or, wait and take a little break so you don't burn out. I miss the days where you had to wait for code to compile or for your "big data" job to run, so you could give yourself a little mini break.
Of course there is a relevant XKCD: https://xkcd.com/303/
Re: Don't Wait for Claude
#26If 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
Why should Claude finish complex tasks in less than seven minutes?
The need for "complex tasks" should be exceptional enough that you're not building your workflow around them. A good example of such an exception would be kickstarting a port of a project for which you have a great test suite from one language to another. This is rare in most professional settings.
Re: Don't Wait for Claude
#27This looks absolutely wonderful. Is it possible to run against Claude remotely (e.g. on a VM?). Or should I ask Claude to add that?
Re: Don't Wait for Claude
#28When computer works, it's sword fighting time. I don't make the rules
For younger people, just in case: https://xkcd.com/303/
And for those scoffing
And for those who are feeling smug, that last one (which I still consider fairly recent) was 14 years ago
Re: Don't Wait for Claude
#29Just show us the prompt you used to produce this post instead of the output
Nice catch. Look at this at the end:
> jc is open source. If you have improvements, have your Claude open a PR against mine. I don’t accept human-authored code.
So it seems not only does the author reject human-authored PRs, they also refuse human-authored blog posts.
Re: Don't Wait for Claude
#30“Don’t pay attention to what Claude is doing, just spam your way through code and commands and hope nothing went wrong and you catch any code issues in review afterwards” is what this sounds like.
I will run parallel Claude sessions when I have a related cluster of bugs which can be fixed in parallel and all share similar context / mental state (yet are sufficiently distinct not to just do in one session with subagents).
Beyond that, parallel sessions to maybe explore some stuff but only one which is writing code or running commands that need checking (for trust / safety / security reasons).
Any waiting time is spent planning next steps (eg writing text files with prompts for future tasks) or reviewing what Claude previously did and writing up lists (usually long ones) of stuff to improve (sometimes with drafts prompts or notes of gotchas that Claude tripped up on the first time which I can prompt around in future).
Spend time thinking, not just motoring your way through tokens.