Is "picking the right tool for the job" truly the responsible approach? Is wanting your tools to be cool really a sign of immaturity? Can we and *should* we still be passionate about Java?
Software development principles have been applied to dating. The Half-Bad-Boy-Plus-Protocol dating design pattern might just get you more than a phone number. But what about the opposite? Are software developers exempt from the fundamental principles of dating? Could software developers have something to learn from those with expertise in the art of the Blind Date?
You KNOW you shouldn't have this much trouble, so you think, "Am I getting stupid, or did someone go out of their way to make this API confusing?" In my case, I probably *am* getting stupid, but I am SO not going to take ALL the blame...
Passion... motivation... enthusiasm. What does it take to get excited about what you're doing, and once you're excited, what does it take to STAY that way? Try to remember how you felt when you ran your first servlet. Your first distributed (RMI) app... with dynamic code downloading. Your first enterprise Javabean. (OK, strike that last one.)