If you’ve learned one type of language, it isn’t difficult to learn a similar one. The hardest part is not the language ‘features’, it is all the crappy bugs that go along with the environment. That is what takes time to learn, and it is never documented (properly). If you get into the habit of continually learning new technologies, it gets easier as you get older (they’re all the same underneath: demented).

Getting a programming job, even a senior one is great, but it gets harder to find as you get older. If you want to survive, you’ll have to broaden you skill set, which also makes you worth the extra money.

‘Programming’ is just one task in building software. Analysis, design, and leadership are actually more important. Most large successful development projects have a ‘lead’ techie with a wide range of skills, as well as several seniors and a few juniors, if they are well-balanced.

Generally, if I apply for a position, then I’ve done some reading and playing with the base technologies long before the interview. I don’t try to bluff or fake it, but it is easy enough to do some reading, installing and playing, so that you at least sound interested.

Paul.
http://theprogrammersparadox.blogspot.com