Good god. Not that it isn't interesting, but how is understanding capacitor timings supposed to make you a better programmer? Good article, poor title.
I agree with Aaron, but I don't think he'd go this far. Programmers concerned with performance need to understand caching and the cost of a cache miss. That's about on the same level as PB and his read heads. The level of detail in this article goes well beyond that and is unnecessary.
I was expecting more about the use of heap space and stack space. That would be more useful to know about for a programmer.
Ulrich Drepper, you rule!
Really looking forward to the next 6 parts of this series.