Re:Ask HN: Why is that 10+ years experience folks struggle t...
by geebee on Wednesday September 10, 2014 @01:32PM
(#8297772)
I think the "industry-wide accepted definition" you've referred to is the key here. There's greater awareness of precisely what "staying current" means, and there's a more measurable and straightforward way to fulfill those requirements.
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.
Re:Ask HN: Why is that 10+ years experience folks struggle t...
by dllthomas on Wednesday September 10, 2014 @01:37PM
(#8297812)
Actually, I think the key might be that tech changes while we still need people capable of dealing (in depth!) with the old stuff. You don't have lawyers that need to practice today in the legal system of 20 years ago. Medicine learns better (we hope) ways of dealing with the same thing, but no one needs to remain an expert in the treatments we've discarded. Tech needs some expert COBOL programmers until it doesn't.
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.