(In response to the article in the link) Every profession has tools and "knowledge capital" that eventually become obsolete; the writer is acting as if software development is the only one. There are many fields of work that experience changes in their associated instruments and disciplines. For example, I doubt you'd find it much of a hinderence as a mechanic these days if you didn't know how to work on a carburetor, or it's inner workings for that matter.
The writer also seems to assume that you become a programmer by simply learning how to use a given language; this is not true either. I knew a programmer who used to help fix problems in code written in java and he has never even learned java. Good programmers depend on thier knowledge and understanding of design patterns and software algorithms. The language is merely a tool or "flavor" - for lack of a better word - used to implement the solution. You will have to use the language they want you to use but hey, thats life. Besides, if you're really a programmer it shouldn't matter anyway; learning new things should be half the fun. Is learning some new syntax really that big of a deal? And, lets be practical here.... How many times do you think you will have to do that in your career? I doubt companies will spend money to change their application simply for it to be written in the newest language available. (And Im being extremley sarcastic here; they will hold on as long as they possibly can) So, maybe three to four times in your career? I dont think it's that serious.
Good Luck.
and narue, your first post was excellent
