heh I agree with you conceptually but I've been in talks that are like (given X is a concept/library/framework) "I don't know about X, but --" "Oh you don't kno

heh I agree with you conceptually but I've been in talks that are like (given X is a concept/library/framework) "I don't know about X, but --" "Oh you don't know about X? We don't want to know or understand anything about people who don't BELIEVE in X. You're disGUSting!" But I never said I personally don't agree with the technique... so the response I go with is "Well, I agree with the philosophy there but my previous employers didn't budget any time for X." which they seem to absolutely hate anyway. The reason I ultimately went corporate was because the hiring practices were more algorithm/concept-based (web services, AJAX practices, software design principles) rather than library or language-specific. I was hired into a Java team without even knowing Java. About 3 months later I found I could program on any part of their stack if they really needed me to. Hiring practices that are not based on assessing a candidate's capabilities strike me as egotistical and pessimistic. I'm going to keep reading theoretical Comp Sci texts to see if I can get to the next phase of my career rather than joining the learn-every-framwork-under-the-sun-OR-ELSE movement.