The other week I read Gergely Orosz’s excellent post on the state of the tech industry in 2026. In that post, several prominent developers share how they work with 5-10 parallel agents, each one running in a separate terminal tab. This is a trend that I think is about to enter the mainstream.

That trend also ties into a topic I’ve written about before: the cognitive cost of faster coding. Back then, I claimed that agentic coding is mentally expensive and more effortful than old-school manual coding. This time, I want to expand and revisit the human consequences of running five agents in parallel. I mean: what could possibly go wrong?

all 2 comments

sorted by: hot top controversial new old
[–] [S] 6 points 1 week ago

The big shift with agents is that it’s now technically feasible — and consequently tempting — to launch multiple workstreams. In fact, the entire agentic workflow actively encourages it. I mean, when launching an agentic task, I never know what the wait time will be. Are we talking 30 seconds, or do I have to watch the internal LLM ramblings for 25 minutes? That wait time is like an open invitation for self-interruptions, which are the most damaging types of context switches. AI coding just gives us so many passive pause points: waiting, reviewing, correcting, waiting again, ad infinitum.

To avoid getting bored, it’s tempting to embark on a second and third task in parallel just to stay busy. This is often a mistake: agents scale; human attention doesn’t.

I can very much relate to this, particularly with my neurodiverse brain that wants to remain stimulated. I've fallen into the trap of launching multiple agents, all working on different projects, and it never works out well as my attention gets fragmented, and I become overwhelmed.

  • source
  • [–] 3 points 1 week ago

    No one doing this workflow is actually coding. You're having machines do the coding. What's being described and complained about here is people being bad at project management.

  • source