After 1T in spend, it's still not clear that AIs will beat out a $30k secretary.
Also, your link has nothing to do with computers.
The link talks directly about the disconnect between the supposed productivity benefits of a technology and the measured productivity benefits of it in practice. And provides historical context about why the “obvious” benefits of a computer did not materialize when it was introduced; business and their processes had to be rebuilt around the computer before real gains were seen.
It's a structural deficiency in the way they work that can't just be handwaived away.
There are new architectures, paper, and harnesses coming out weekly that improve performance, accuracy, and/or performance efficiency.
Whether they can do better or not than a secretary is a poorly defined metric. But by objective metric they are already producing less buggy code than $30k developers, and doing it faster.
The perennial reality is that automation is inherently inflexible, so there's only so much of it that you can do before you've committed a huge strategic blunder by making your business resistant to change and severely curtailing its ability to cope with situations that don't cleanly fit the mold. So then we need to hack in ways to deal with the exceptions, but, since they're hacked in, they're often painful and time consuming. Sometimes so much so that after the new process stabilizes it turns out to be even more cumbersome and require more manual effort than the system it replaced.
When anyone other than a technologist suggests doing that kind of thing, we call it "bureaucracy", and we hate it. I think maybe what we have trouble seeing is that there's actually a pretty fundamental difference between automating purely technical processes like server deployment, and automating processes that are fundamentally about mediating human interactions.
It doesn't have to and I'm pretty sure it won't.