It's interesting to me: This talk was much broader than any talk I've heard from him before. I can imagine watching this and thinking "this is all pointless fluff", if I were in a certain mindset. But having worked on a project for a while and encountered this exact problem, I think this talk is genius. (Because the non-fluff, the concrete examples are coming from my own experiences.)
Everyone should watch that talk. It's the most compelling I've yet seen for the relevance of applicative programming. I was not convinced, but I was closer than I've ever been to being convinced.
I don't know much about Clojure (I wrote my last Java/Lisp code years ago) however I strongly recommend this talk to every developer. As good as it is at clarifying the development process, I also enjoyed it a lot too because it was thought provoking and funny at times.
Clearly Rich failed at fitting the whole of his talk into discrete Tweet-sized portions. For a talk about thinking through problems you would think he would have thought about that angle. Sheesh.
About four minutes in he gets to what he's actually going to talk about.
For anyone who doesn't want to skim through to get an idea, he talks about his philosophy on thinking about the problems he's working on rather than always going straight through them. When you spend some time away from the computer just thinking about what you're working on, or working through completely separate problems every other day, it gives your brain time to process all the separate components that are too big to fit in your working memory at one time. This allows you to create connections during the day (or after a night of sleep) that lead to seeing the problem and its solutions in a new light.
