My industry is defense/aerospace, which doesn't engage in age discrimination as much as the wider 'software industry' does.
Part of the reason I can't seem to land a real lead/architect position (despite what my title says) is that I'm waiting on all the boomers currently parked in those positions to die/retire.
Agree this is a problem. Here's how we make it work:
Work with great people. Also code reviews make sure new dependencies don't usually in unless the team agrees (we are a reasonable bunch).
Standardized on Angular. It seems to me Angular has less churn. Yes: there is a life cycle and we have to follow the releases but it is mostly well documented.
>Second, you've got to take into account that NN/ML/AI et. al. is going to "eat" a portion of all programming work within the next fifteen years or so.
Are there any repos I should look at to learn this? How is this possible when even humans can't read sarcasm online? I'm genuinely blown that this is even possible?!?
> It turns out that a large portion of real-world problems have the property that it is significantly easier to collect the data (or more generally, identify a desirable behavior) than to explicitly write the program.
> The pattern is that there’s an existing software project doing data processing using explicit programming logic, and the team charged with maintaining it find they can replace it with a deep-learning-based solution.
It's really unfortunate I know all too well how this feels. How do you hedge since you are nearing "old" in industry?