Thread

1. epistasis · 1791063596 · focus · HN ↗

   I really hate long tasks. Claude never gets things right, at least for me, and wastes tons of time when a simple question would have gotten me to the right result rather than several turns of correcting bad decisions in addition to the long amounts of wasted thinking time.

   What sort of workloads do well with these long tasks? The big labs are optimizing for long run time on their own, but it seems like a terrible thing to optimize on unless you're trying to do something like prove a hard math theorem, which success is clearly defined and the route doesn't matter a ton.

   Plan mode has been made increasingly useless. I need to discuss to iterate to get the desired design, explore options, because Claude never gets it right first try and I don't have enough knowledge of options to specify everything up front.

   Ah well, the Chinese models will still work well, I guess.

   1. Merad · 1791084823 · focus · HN ↗

      Use the superpowers plugin. It's a game changer. You start by building out a spec defining the work you want to be done, then claude writes a detailed implementation plan. It can easily work for hours without interruption, and the process integrates testing (TDD when possible) and review steps along the way. I even did one fairly complex POC for work that had claude implementing for almost 3 days straight, with me stopping it and handing off to a new session when context hit about 800k. The process is slower and more methodical than the way claude works by default but the output is much better.

Unofficial Hacker News client; not affiliated with Y Combinator.