Peter Seibel tried to "unpack some of the context," it's probably a good place to start for anyone who's interested:
http://gigamonkeys.wordpress.com/2009/09/28/a-tale-of-two-re...
If only wishing made it so!
It makes sense when dealing with surface details in rapidly changing web APIs, but otherwise that approach condemns programmers to starting from zero and wasting time re-discovering fundamentals.
"Mathematicians stand on each others' shoulders and computer scientists stand on each others' toes." — Richard Hamming
While I've been programming since I was a kid, my academic background is in history - Viewing the industry through that lens reinforces how it's collectively in an early phase where people still fall to their deaths trying to fly with wings made of wax and feathers.
There have been plenty of people with real breakthroughs, but the average programmer probably hasn't even heard of them. I mean, their work is already obsolete, right?
If more programmers actually read stuff that was published longer than (gasp!) five years ago, perhaps there would be less naive noise about how New Methodology X is going to finally fix all these nagging issues in software development once and for all.