This article also leaves out:

- waiting for compiles

- waiting for the CI server to finish running tests

- waiting for network transfers

- waiting for VMs to spin up

- waiting for slow algorithms to process data

- et cetera

Even if it were physically and mentally possible to problem-solve 16 hours a day, we are still not at the point where our processes and machines can keep up with us, and we probably never will be. The dev-test cycle in itself is very time-consuming and repetitive. I don't know any way of solving this that doesn't involve spending even more time writing a lot of unit tests.