Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Don't Wait for Claude

jeapostrophe.github.io

Post reply on HN
Print view View original

11–20 of 67 posts

Re: Don't Wait for Claude

#12

Post by hirako2000 »

rybosworld wrote: post #9
polyterative wrote: post #2

Don't really agree, in my experience the switching context is extremely costly. I personally have trouble having even a couple of sessions running in parallel,Especially when I'm talking difficult hard to solve problems. Of course it's easy for trivial jobs, but it's not always the case. I have been much more successful in making my time worth by taking a look at the model's output and actively participating.It gives…

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.

Perhaps they earn $500k and worry spending any less than $250k in token may raise suspicion.

Re: Don't Wait for Claude

#13

Post by samename »

bwestergard wrote: post #7

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

Why should Claude finish complex tasks in less than seven minutes?

Re: Don't Wait for Claude

#15

Post by flakiness »

The old saying is "don't multitask" but apparently that time is gone.

I wonder what people think about this. I know there is a class of SWE/dev who now consider oneself as "the manager of agents". Good luck to them and articles like this would work for these people.

I'm not there yet and I hope I don't have to. I'm not a LLM and my mental model is (I believe) more than a markdown. But I haven't figured out the mental model that works for me, still staring at the terminal Claude blinking the cursor, sticking to "don't multitask" dogma.

Post reply on HN