Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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


But those things won't be sped up by a faster LLM, so I feel like that's not what the OP is talking about.


Well, 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.


Or slow MCP servers that are waiting on HTTP calls from APIs, playwright/other UI instrumentation, etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: