‹ BackHN Continuity

Thread

Getting the most out of Opus 5.5 in Claude and Claude Code

232 points · 156 comments · saikatsg

  1. rdli · · focus · HN ↗
    It’s a really good model. Over the past few days, I give Opus some general directives to basically speed up our CI, and telling it I care both about billing minutes and wall clock time. I told it to create a plan after analyzing everything in our CI, run the plan by a Fable subagent, and then focus on low-risk, high-reward changes.

    9 hours later, I had 12 PRs ready to be merged, and the net result is CI time has dropped from ~10 minutes to ~4 minutes, and billing minutes have dropped around 60%. Less than an hour of my attention.

    1. GroksBarnacles · · focus · HN ↗
      Is "wall-clock" an actual term you used before Claude? I had never heard it before the model used it and I can't stand it.
      1. hazard · · focus · HN ↗
        It's a pretty old term, to distinguish from e.g. CPU time. This was in common usage even 30 years ago.

        Example from 15 years ago: <a href="https:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;7335920&#x2F;what-specifically-are-wall-clock-time-user-cpu-time-and-system-cpu-time-in-uni" rel="nofollow">https:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;7335920&#x2F;what-specificall...

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.