7 ms·
You mentioned "coming back later" but being in the zone. That's the part I want to understand. So this metaphor isn't helping cause the conductor is constantly
by majormajor 17d ago
You mentioned "coming back later" but being in the zone. That's the part I want to understand. So this metaphor isn't helping cause the conductor is constantly working, constantly seeing the output. Not coming back later.
- ceejayoz 17d agoMy zone is the big-picture zone. What are we building, what needs to be done, how do the interrelated bits all come together? I can tell an agent "go implement X" and start planning Y that comes after it. I don't really get in the zone for raw code typing, that's always been a slog.
- majormajor 14d ago> My zone is the big-picture zone. What are we building, what needs to be done, how do the interrelated bits all come together? I can tell an agent "go implement X" and start planning Y that comes after it. Well hang on, why wouldn't you just have another agent planning Y for you? And then just come back and review what it comes up with?
- dom96 17d agoI cannot imagine being able to plan the next thing when I don't know what issues the coding agent might run into with the previous/current task. It feels like a waste to be planning the next thing when my previous plan may turn out to be wrong. The only thing I can really think to do is to wait for the agent to be finished, which makes getting distracted by social media and other random stuff really easy. Total opposite of being in the zone.
- ceejayoz 17d agoI can't imagine free soloing El Capitan, but there's a guy out there doing it. My artistic skills cap out at shitty stick figures. I get more distracted if I attempt to focus on just one thing for a day. Different brains.