Love the point that the compiler can only solve problems in the 1-10% problem space. The 90% problem space is our data access which is all about data structures and algorithms. The summary is he shows how instruction processing can be dwarfed by cache misses. This resonates for me with what I've seen in the field with customers in the high-performance space. Obvious caveat is applications where time is dominated by IO.
Follow this with, "...any one who says premature optimisation right now can leave the room - that is the most abused quote of all time."
As he begins closing he makes the comment - "the bad thing is we have a culture that thinks it is a good thing to hide the real problem, we pile more and more stuff to hide how memory is accessed, how memory is arranged, to hide the most significant problem we have to deal with..."
The final quote he gives to Christer Ericson:
"Design patterns are spoonfed material for brainless programmers incapable of independent thought, who will be resolved to producing code as mediocre as the design patterns they use to create it."