How do you balance resume-driven-development with staying current?
Considering that I believe that the best way to effectively gain experience with a given technology is to work, how do you make the decision between "I'm implementing our next project in x because we need to" and "I'm implementing our next project in x because I want to/think it's awesome"? I get that it's about using the 'best tool for...