This tracks my experience, though I haven't gone into the "swarm" approach. One thing I don't think gets enough discussion is: > The cognitive load of this new

This tracks my experience, though I haven't gone into the "swarm" approach. One thing I don't think gets enough discussion is: > The cognitive load of this new state was immense. After about three hours of intense orchestration, I would feel completely burnt. I definitely feel that. It's like the job becomes solely architecting the system (not terrible) but you still need to hold the entire program in your head (deeply taxing) while it is updated by a 1,000 tiny cuts which can dislodge your mental model... and then you are screwed. It is important center yourself from time to time and ensure you are on solid ground. The best way to do that is to give things a minute to sink in. Unless I am boilerplating everything, I don't WANT to go faster. In general, I don't have a lot of desire to go down this orchestrator path. Maybe once tooling and things settle down a bit it can be helpful at times, but usually I get more value from letting things breathe, especially if there are structural changes or new ideas that bubble up and need to be considered. Before LLMs, I would never re-architect on the fly, but I am more willing to make structural changes mid-flight now because it is so costless. Things I used to architect "good enough" (with a plan to revise in 12 months now) can be done precisely right the first time after going halfway down a path then noodling on it for an a day or so. This is "Not the Way to Architect," but it sure is an effective way to go from idea -> complete.