Reviewing agent output arriving faster than you can inspect it
It's a curse I know, parallel lanes, context switching. We're told to aim for surgical precision, one item at the time. But when the world is keeping endless inspiration, software commoditised it's hard to live by the r…
以下正文同步自 Hacker News 最新，版权归原站所有，已转换为易读排版。
It's a curse I know, parallel lanes, context switching. We're told to aim for surgical precision, one item at the time. But when the world is keeping endless inspiration, software commoditised it's hard to live by the rule.Running several agents at the same time, I found myself having a hard time catching up on everything produced, and giving proper feedback. I tend to actually ask my agent to go through transcripts to find old unfinished tasks and re-state the outputs.MD files became tedious, screen shots didn't show the entire flow, production code was usually stale or on stuck on a branch.People out there, do you keep to the rules of capping context switch, or what's the best way to review output here? Comments URL: https://news.ycombinator.com/item?id=50248804 Points: 2
Comments: 0
正文由 探How 从来源站点 RSS 同步，内容未经改写；遇到排版缺失或需要图片、视频时请以原文为准。