Brandon Rhodes' talk "Classic Design Patterns: Where Are They Now" is a good critique of the "Gang of 4" Design Patterns book that dominated software design thinking for decades. Why should you give your attention to a critique of a book from 1994? In part because the critique gives concert examples of how successful design solutions become molded into programming languages and how programming languages outgrow the limitations that originally necessitated the design solution.
I don't know of the speaker, but he seems to speak at many Python conferences.
