One can just as easily make the counter-argument people understand theory, not computer instructions. So the cleaner and more functional your code is, the easie

One can just as easily make the counter-argument people understand theory, not computer instructions. So the cleaner and more functional your code is, the easier (and faster) it becomes for other people to build on top of / around it. But that counter-argument only works given that the current application requires tons of people of work on your code. Just as the article's argument works only if you actually need to squeeze out those extra ms on your 1 machine. My only take away from this is "use the right tools for the right job".