At least, that's the way I always interpreted it.
Just because you learn a new language or technology doesn't mean you become better at problem solving. It just means that you can solve problems using a different tool.
Lawyers and Physicians, Dentists, Nurses, and Dental Hygienists, they all do have to stay current - in fact, I believe that they are legally required to stay current. Now, HN is a tech board, so we don't hear from nearly as many Dental Hygienists here, but I'm going to operate on the assumption that DH's, at age 41, don't encounter the same issues of obsolescence as software developers do.
I think that a big part of this may be something Michael O Church described as "dimensionality" (in an essay on the relative scarcity of women in programming).
http://michaelochurch.wordpress.com/2013/09/21/dimensionalit...
The dimensionality may be a factor here… just as the path to becoming a programmer is much more vague and subjective than in many other fields, so is the path to remaining relevant as a programmer. It's not that it's strictly harder, it's that it's much more ambiguous.
Because they are required as a condition of professional licensing to stay current (and have a documentary trail of staying current that matches and profession-wide accepted definition of what "staying current" means), which means that while there is some risk of being in a specialization for which demand is reduced, it is virtually impossible to not stay current in the manner expected in the industry without voluntarily choosing to abandon the profession. Consequently, its harder to have covert age discrimination with "not being current" as an excuse.
> The dimensionality may be a factor here… just as the path to becoming a programmer is much more vague and subjective than in many other fields, so is the path to remaining relevant as a programmer. It's not that it's strictly harder, it's that it's much more ambiguous.
Sure, but I don't think that is anything inherent in the subject matter ofprogramming that is less clear cut than, e.g., law, in those terms. Its just a difference in the social and regulatory context.
That doesn't mean it isn't rigorous - getting through nursing graduate school and getting board certified as a nurse anesthetist is very rigorous! But my guess is that the path is much clearer. You don't end up getting surprise interview questions about the Fourier transform because you claim to know how to interpret ultrasound.
Personally, I'm 41 with 15+ years of IT experience and I have never felt any sense of age discrimination at all. But, I'm also constantly working to keep my skills current, and I do a lot of things to make myself attractive and known in my area - speaking at events, writing articles, blogging, etc. shrug
My feeling is, if you're sitting at 15 years of experience and you've been, for example, writing Java code for 15 years, go pick up a Scala or Clojure book, or learn R or take the time to learn Hadoop, Spark, Storm, Kafka, MongoDB, etc. If you have skills that are "hip" at a moment in time, I don't think it's usually going to matter much how old you are.
OTOH, if you are a 15 year Java programmer who is still writing Java 1.2 code for a JSP based app that integrates with a COBOL book-keeping system on an IBM S/360, and you refuse to even look at that "new fangled" Java 1.3 or newer, then yeah, you might find yourself in a tough spot if/when they decide to turn off that mainframe.