since the average result is still about 25% faster (my gut feeling based on what I've 'written' the last few months working with Claude Code) it's just very tempting to pull that slot machine lever
Huppie on Hacker News
average result is still about 25% faster
In the thread “Why the push for Agentic when models can barely follow a simple instruction?”, replying to this comment
Helped: Small tasks during meetings allow refactoring without context switching.
Got in the way: Reviewing output often takes as long as writing it manually.
… Now I think the problem is that the response is akin to gambling / conditioning in a sense. Every prompt has a smallish chance to trigger a great result, and since the average result is still about 25% faster (my gut feeling based on what I've 'written' the last few months working with Claude Code) it's just very tempting to pull that slot machine lever even in tasks that I know I will most likely type faster than I can prompt. I did find a place where (to me, at least) it almost certainly adds value: I find it difficult to think about code during meetings (I really need my attention in the meetings I do) but I can send a few quick prompts for small stuff during meetings and don't really have to context …