Thread

1. rdli · 1791060574 · 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 · 1791062324 · 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. Klathmon · 1791062637 · focus · HN ↗

         I've used wall clock for many years, normally when compared to CPU time when talking about parallelizing some process.

         CPU time might go up while wall clock time goes down

Unofficial Hacker News client; not affiliated with Y Combinator.