I was reading this article that is doing a pretty good job at explaining in what situations an IoC container saves the day. And even though I dislike most uses of IoC containers I've seen I have found them useful once or twice.
I once was working with a company that complained that my code was not optimized because it used 100% of the CPU. So I asked if the user interface was responsive. And it was. So I asked if they experienced any noticeable delays in responses. They didn't. So I asked for how long the CPU was at 100%. And the answer was...
Last year Michael Feathers wrote an article about unconditional programming which in essence is just an idea to avoid any type of control structures since control structures tend to make code harder to understand. This is not a new idea.
Configuration files is something we have always been familiar with and with cloud services I think more and more configuration has started to move into code. But I was very intrigued by yet a different concept used by a team I worked with a while back; configuration APIs for temporary changes.