not OP but usually for me this means long verification loop; waiting 10min on CI checks, that kind of thing, rather than actual 1hr wall clock of token generation
replyBut those things won't be sped up by a faster LLM, so I feel like that's not what the OP is talking about.
replyWell, I used an extreme example. OTOH, I’ve done quite a few of those „fix CI” or „migrate X” prompts recently and while there is a fixed component like running CI / builds, I’d say the LLM time is still around or above 50%, especially at the beginning of the project. Then there’s also regular tasks that now take minutes per message which completely get me out of the zone. I imagine iterating on those in near real time would be a big change.
replyOr slow MCP servers that are waiting on HTTP calls from APIs, playwright/other UI instrumentation, etc.
replyI’m rewriting our integration test suite to run tests in parallel. I have the changes split across 7 branches, and each needs to be fixed to have no flaky tests. I told it I want 3 consecutive CI runs with no flakes and no artificial fixes / assert removals etc. We’ll see what comes out; it’s almost a side project so there’s not much to lose other than some of my weekly limit that resets soon.
reply> a side project so there’s not much to lose other than some of my weekly limit that resets soon
replyBasically the entire token-maxxing AI hype train in a nutshell. Lovely!