3 ms·
I can't reach flow with agent coding because as soon as I set it running I flip over to something else and come back later. I think this is a problem with the
by qingcharles 1y ago
I can't reach flow with agent coding because as soon as I set it running I flip over to something else and come back later.
I think this is a problem with the current agents, though. If it responded immediately with its ideas and code then I wouldn't flip away and could stay present.
- deleted 1y ago[deleted]
- panarky 1y ago>> non-participation > flip over to something else A flow state is possible with 100% focus at any level of abstraction. If you just "flip over" to HN while the agent thinks, then you're not 100% focused. But if you're managing three agents at the same time on the same codebase, and while Agent 2 is thinking you "flip over" to Agent 3, you're still fully participating, just at a higher level of abstraction.
- Philpax 1y agoI would like to believe this, but in practice, the context switch involves purging my mental working state, which drags me out of the flow state. I'm not sure how to solve this, but I imagine that the context I switch to should be as close as possible to the one I started with - the problem then is that the agents might trample over each other.
- TZubiri 1y agoRight, same deal as if you were running multiple requests over the network, you need to parallelize them instead of idling while you wait for the network to complete.
- mrtesthah 1y ago[flagged]
- qingcharles 1y agoThe agent is stuck doing something for multiple minutes. Am I supposed to just watch a spinner? ┐(´ー｀)┌
- tomhow 1y agoPlease avoid swipes like this in comments on HN. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html