Sounds like they want to halt progress so they won't be forced to hit the books and learn something new. Sorry, but you don't go into IT and expect things to stay still.
>>Sounds like they want to halt progress so they won't be forced to hit the books and learn something new. Sorry, but you don't go into IT and expect things to stay still.
Exactly. I myself took this route: Bought the VB.NET web apps certification book, created about 300 flash cards with defintions and concepts I didn't know... Spent weeks studying.. Then started to make my own on-line web app.. Then got a .NET contract, worked my tail off to put what I memorized into practical use.... and after about a month, I was doing fine...
It takes work, and these people are whining about having to do something extra to stay ahead. I'm surpriesed they aren't complianing that VB3 isn't supported any more.
I LEARNED THE HARD WAY WITH C# -- I put off learning it until last Q of 04-- and it was a mercy project -- had it not been for that I would not have gotten the gig... Looking at the job market, I have tons more C# offers than VB... And C# hasn't been in practical use for more than a year or so in most places, so I'm not toooo late. These people are gonna be way behind the curve when C# is the "defacto" .NET language and they have just barely started .NET v 1.0....
In this age of outsourcing, one MUST keep on top to stay afloat...
As an EE, there is a difference between someone who knows a programming language, or even a type of technology, and someone who can really wield it elegantly.
With some languages, it just takes enough time 'in grade' to get that proficient with a language.
Something to be said for the workmanship that can be had by such people with expertise in languages that are 'just behind the curve' a little.
I remember when being a power engineer was the very last thing you wanted to be. Now they are making $150K per year because nobody was interested in it.