What I am saying is that low level thinking such as depicted in the article has little to no value to the programmer.
Performance-optimization/OS kernel/HPC inner loops/Power-sensitive code (think mobile devices)?
pacemkr isn't saying all low level info is useless to programmers, just the article's focus.
Part 5 deals with cache optimization. Part 6 deals with multi-threaded optimizations. Other parts deal with various layers of the memory hierarchy (VM, caches etc.)
I, personally, only take issue with the EE-heavy portion; it only serves to obfuscate what's important with way too much (programmer-)useless info, and maybe to scare off people who could otherwise benefit from the rest of the article. I'm fairly certain that the OP of this thread views it the same way, as they mentioned:
"I've enjoyed it all, but there is zero reason for a programmer to know almost anything from that page. You can make phenomenal software without ever knowing what a transistor looks like on paper;"
implying just a single page (the one linked), and EE-only content.
Higher level thinking, more expressive languages and tools don't preclude you from looking at low levels of your abstractions.
Edit: Looks like we were talking past each other. I was talking about the complete article (the non-EE bits are about VM, cache, NUMA awareness, memory management for multi-threaded programs etc.) The tail end of the OP's link, links to the rest of the parts.