If you notice, a lot of these people in that article are in hardware design: electrical engineering, probably Verilog and the like. A lot of that work has successfully been outsourced which I think is the real cause of the decline. I suspect it didn't look like it was a particularly bad field to be in until it suddenly wasn't.
It's a long way from webdev though. And yeah these are presumably smart guys who could pick up webdev, but could they make the career transition without getting bumped back down to Junior by the hiring manager? And who wants to hire a 45 year old junior web developer?
There was an article recently about YCombinator shifting its investments to biotech. Suppose webdev dried up and all the funding started flowing to biotech. I'm sure I could learn what I'd need to know and I bet you could too, but could we head over to the biotech companies and sell ourselves as "middle aged web guys, self taught biotech engineers (no experience)?"
Of course with 20 years of development experience and 5 years of teaching experience, I had a lot of other things to sell as well. I certainly had no lack of interest and had positions to choose from. I did take a fairly healthy cut in salary, which seemed reasonable to me since the company that hired me was taking a risk. I was careful to pick a position that would work well for me and I did not take the highest offer. I definitely feel that the investment I made at the beginning was definitely worth it.
I think as an older person moving into a different area you have to be able to convince people that you will pick things up quickly and that your other attributes are worth it while they wait for your technical skills to come up to par. If you are careful to build the kinds of skills that will be valuable throughout your career, you will have relatively no problem in my experience. The people who have trouble are the ones that were just scraping by in their original positions, or people who had a laser focus on a particular skill set that is no longer valuable.
This begs the question: how did you manage to get those interviews?
If anyone looks at the code, it's pretty crap, but it shows that I like to write code.
Also, because I knew I was going back into IT, I built: http://mikekchar.github.io/portfolio/
It contains a bunch of egotistical musings about software. It shows that I probably think too highly of myself, but that I know how to write English fairly well ;-)
Also, after I moved to London, I made a point of attending events where I could make contacts. My return to IT was complicated by the fact that most of my career was in Ottawa, Canada. Since my family was moving to the UK, my contacts were useless to me. I got 3 interviews in as many weeks from simply meeting people at the pub.
As far as I'm concerned, these activities are "selling myself". The fact that I also enjoy them is beside the point (especially drinking beer and chatting with other developers ;-) ).
Lately I've been working on trying to allocate time to my side projects. As you can see, I haven't updated my previous projects in a very long time. However, it is vitally important.
In the end, the job I ended up accepting was through a head hunter. No idea how he got my name. Probably should have asked him ;-).
Having said this don’t worry, if you think the job prospects are bad for old developers they are far worse for old scientists.
If you look at current jobs such as "bioinformatics programmer", the salaries are somewhere between a biologist and a software engineer even though it requires more knowledge than either. Remember, biologists start off at around 35-50k/yr on jr. level, while SEs start at ~100k+.
Basically, it is better to be a junior level SE than a super senior bioinformatician.
The real problem with biology is the salaries don’t rise as fast you become more more senior. Biotech is certainly not the easy way to wealth.
One reason I am glad I got out of biotech.
Anyways, thanks for sharing.
It doesn't usually require more knowledge. The majority of bioinformaticians that I know are pretty poor coders, and know just enough Perl or Python to count some stuff up an do some stats on it or plot a graph. They have no idea how to set up a server, write maintanable code, design a database well or keep a website secure. Obviosuly there are exceptions, but the majority that I have worked with are junior level programmers with knowledge of biology.
I am not sure you fully appreciate what " knowledge of biology" means. As a programmer who did a lot of molecular biology in the past - doing molecular biology is not simple. The learning curve for a lot of biological topics - especially the ones that get close to organic chemistry is really steep.
Programmers underestimating the value/knowledge of accountants/lawyers.
Businessman assuming tech work is simple.
People by default assume what looks simple for someone to do must be simple - even if they spent 10,000+ hours practicing it.
A lot of bioinformatics is implementing elaborate algorithms in a memory efficient way.
Things like
- approximate string search using modified suffix trees
- some new variation of the EM algo using a new optimization strategy
- the whole protein folding field where many implement the simulations on a huge array of GPUs. Here you not only have to know how to write efficient code on GPUs, but also be an expert in parallel algorithms if the algorithm you are implementing is not embarrassingly parallel.
However, these algos will be thrown out in a month so they don't care about maintainability or uptime.
That sounds pretty awesome, actually. Who wouldn't want to add that wealth of experience to their web repo?
That smacks of pure ageism to me. Just recast it to a racial context to see:
"And who wants to hire a black junior web developer?"
On the other hand I often feel like the bar for keeping up can be extremely low ... at work I am back to using Unix-derived systems after some 30 years. And emacs, again 30+ years. And C++, over 20 years. You get the picture.
I usually have to resort to my own projects to learn something really different.
My latest example of this was learning Scala 5 years ago. Bet on something new, and then you get calls from all over the country to work on it, as most people are trying it, but few know what they are actually doing.
As a young dev, I really want to learn how to do this. I'm a newcomer to the Scala party, but I can definitely see it becoming a huge player and there are so many reasons - Odersky has basically a team of PhDs at EPFL constantly making awesome stuff for the language and they have made some incredible stuff - TASTY + scala-meta is one of the latest, Scala.JS is another, and really the list goes on and on.
But I'm only beginning to clue in on this now. Would've been great if I had jumped in earlier. If you don't mind me asking, how do you learn to pick the right horse? What were the signals for Scala? my guess now is the fact that Odersky was a major contributor to Java and built both a strong technical team and corporate backing, but thats hindsight ofcourse :)
Beyond that, language/technology specific Meetups, mailing lists, github repos, and even IRC are a great way to be noticed.
The last thing is that, especially for a new or niche specific technology, it really helps to be in one of the tech hub cities. Remote work is often available however it requires more self promotion (IMO) than being on site.
Yeah, but should they be tossed aside for that? And should everybody be expected to keep up against fresh-out-of college people?
Maybe the speed of technology change can be a problem, especially if it starts putting out of a job more people than it employees, and no counter-measures (e.g. citizen's income, etc) are in place.
Not to mention that a lot of this "technology change" is just changes in fads, and there were perfectly good technologies 20 and 30 years ago that are even better than the latest BS du jour at what we do now. Just ask pjmlp!
I am not quite as old (45) and I still love learning new things, but it does take more effort than when I was younger.
Absolutely true, and it's also fair to say that I have to work harder now to remember things that I could recall effortlessly twenty years ago. Fortunately the development of the Internet into a global knowledge store perfectly coincided with my getting older :). I know most developers couldn't work without the Internet these days, and that's doubly true for me!
I still remember trying to write assembler back then by memory poking to speed up the inner loops of my BASIC programs. The crazy thing is occasionally I would get it to work despite having (almost) no idea what I was doing.
But there are 100 javascript frameworks that all do the same thing! After a few years you will stop being motivated to re-learn re-inventing the wheel too. But all the jobs expect you to know whatever's hot right now. That's not engineering, it's fashion.
I vividly remember a manager (50-ish himself at the time) screening resumes once, letting out an exasperated sigh at the sight of one: "this one was born in the 60's, jeez!". I was the ideal age for a programmer at the time so it didn't affect me, but it still shocked me.
(I know it's customary not to include a date of birth on an American resume, but they'll still figure it out from dates on your diplomas, work experience etc)
It means that anyone can learn a programming language and become as 'competent' as the 55 years old. When you have a choice between a 22 year old and a 55 year old, equally competent, who of the two is a better bet ?
1. save time
2. save money
3. make money
No rational employer will look at a time saving, money saving, money making candidate and think "this person appears to be too good a match for my business needs".
Business value trumps ageism. Most the candidates I couldn't place typically didn't focus on trying to be profitable employees.
It can always be daunting when new tech comes out and hard to be a newcomer in an area you have so much experience in, better to embrace and learn or consider another line, as apposed to be a grumpy ol' stubborn git ;`P
Managers don't seem to make more either, so it seems you have to be specialized and have a really impeccable resume (and that doesn't mean having Microsoft and Apple and Facebook on it.)
I guess it's for the better. Flipping burgers is probably in my future, and I am pretty happy with it.
For my own part, this is still what I love to do. I'm busy 10 or more hours a day and at least eight of them are spent with some technology I knew nothing about six months ago. I was layed off from another startup at the end of September and started this current gig three weeks later. We just finished five weeks ramping up on Google Container Engine, during which time I also learned to use GNU make for the first time, and learned about etcd and Google Compute Engine. What it boils down to is this: stay interested, and stay current, and you stay employed. If those things are not within your power you no longer belong in this craft.