"how to fill the minutes that AI takes to write code"
I usually review the code that's been written. Sometimes directly, sometimes by telling claude to bring things up piece by piece to explain choices as I review. Or I kick off one of the various maintenance tasks, validate my assumptions and expectations on how things should function, note the things that don't to be addressed. I'm going to have to do this stuff anyway, I might as well do it then.
Or I read something, or do something to clear my head. Sometimes because I need a mental break, because I find that the speed these tools having me working at can be taxing in different ways.
I think expectations of the "10x" variety whether you put that at 10 or 3x will have to be adjusted. Coding as fast as 5 developers is far far different than "A singly developer can produce as much as 5 others"
+1 review the code
Screw {some number}x. Such BS. Those who can, do. Those who can't, write and spread pseudo-intelligent brain worms. Reject!