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. woodruffw · 1791062484 · focus · HN ↗

         “Wall time” is a pretty common systems term (you see it when comparing total runtime to kernel time, for example). I wouldn’t have indexed on “wall clock time” or other variants as an LLMism.

Unofficial Hacker News client; not affiliated with Y Combinator.