The Bottleneck Moved Again
For two years the industry treated AI as a productivity multiplier for writing code. Faster code generation was supposed to shift the constraint to design, then to verification. Rachel Laycock, CTO of Thoughtworks, watched the constraint keep moving and concluded that the real bottleneck is no longer any of those stages. It is human attention.
From Flow State to Orchestration
The best developers she observes no longer spend long uninterrupted stretches in deep flow. Instead they run multiple agents in parallel, assign work, supply context, evaluate results, and decide what needs another pass. Numbers of eight, ten, or twelve concurrent agents are already common. Beyond that point the human becomes the limiting factor.
Laycock compares the role to that of an orchestra conductor. A conductor can play the instruments but chooses not to. Value comes from holding the entire score in mind, bringing sections in at the right moment, and adjusting tempo and balance as the performance unfolds. The same skill is emerging in software: deciding which agent tackles which problem, spotting subtle mistakes, and protecting the overall coherence of the system.
Energy Management Becomes a Core Skill
The parallel with executive work is striking. When Laycock became a CTO she discovered that managing energy mattered more than managing hours. Constant context switching and incomplete information are the daily reality. Software developers are beginning to face the same cognitive load. The industry has decades of experience coaching leaders through that environment; it has far less experience preparing individual contributors for it.
The shift does not mean developers become managers or that AI replaces engineering judgment. Engineering expertise is simply applied at a higher level of abstraction and at higher frequency because execution itself has become cheap. The scarce resource is the ability to direct that execution wisely without burning out.
Laycock’s essay is an early attempt to name the change so that teams can start redesigning the job rather than only the tools.