I was watching a channel 9 video earlier by some members of the C# design team, including Anders Heijsberg and Eric Lippert, and one of the recurring themes was one about programming for concurrent processing. (Video is here http://channel9.msdn.com/posts/Charles/C-40-Meet-the-Design-Team/)
Of course the holy grail is for a developer to be able to cut code as if it were to be processed in a single thread, and then for the framework to run it cuncurrently when its deemed safe to do so. It's pretty clear though that the holy grail is not that close yet, sure we are talking about it and things like PLinq are already in beta but we are not there yet, largely because this is a very difficult problem to solve. One thing that the video did bring home to me though was the fact that I have not really turned that switch on in my head yet, I have of course written threaded apps, but only when its been very necesarry for a specific task, mainly because its hard to write, and its hard to maintain, concurrent programming is not yet a regular tool in my toolbox, I think I need to address that.