Live data from Hacker News

Don't Wait for Claude

jeapostrophe.github.io

31–40 of 67 posts

Re: Don't Wait for Claude

#31

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.

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

Something would be deeply wrong!

Re: Don't Wait for Claude

#32

Just show us the prompt you used to produce this post instead of the output

I disagree with this take. I get that LLM produced text is filled with crappy, over the top writing in pretty much all cases, but if a prompter/writer/blogger is using it iteratively, the LLM output is going to be way better than their writing. Also, if a person is using LLMs to write articles, do you really want to see their likely even worse writing?

Re: Don't Wait for Claude

#34
post #29

Just 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.

I wonder if they also only want agents to read it, not people.

Re: Don't Wait for Claude

#37
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.

Re: Don't Wait for Claude

#38

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 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://pmc.ncbi.nlm.nih.gov/articles/PMC11543232/

I've tried hard to stay away from Instagram, TikTok, etc - for this very reason. Now my day job is going to be attacking me in much the same way? Great.

Re: Don't Wait for Claude

#40
I don't know how and if people really manage to run many tasks in parallel and also not check the output. Very recently I had two items that for a reasonably intelligent engineer wouldn't be very complex, but would take time to implement.

One of them was vibe-coding an Electron app for myself that was running a Llama server. Claude couldn't find out why it wasn't running on Windows while it worked fine on Linux and Mac. I obviously didn't check all its output but after several hours had a feeling that it was running in circles. Eventually we managed to cooperatively debug it after I gave it several hints but it wasted a a lot of time for a rather simple issue which was a challenge for me also because I didn't know well how the vibe-coded app worked.

The second one (can't go into details) was also something that's reasonably simple but I was finding awfully many bugs because unlike the first app, this one was for my job and I review everything. So we had to go back and forth for multiple hours.

How can someone just switch to another task while the current one requires constant handholding?

Post reply on HN