3 ms·
There's definitely a lot of age bias in the employment, particularly after ~40. The key is to move up the difficulty ladder. Your age-resistant employment prosp
by adventured 8y ago
There's definitely a lot of age bias in the employment, particularly after ~40. The key is to move up the difficulty ladder. Your age-resistant employment prospects skyrocket if you move away from lower value skills - think PHP - and move up to (just for example) Java or Go et al.
Or move away from low value front-end junk that turns over every three years (the latest JavaScript framework of the month), and to higher value serious programming. That's where long-term job security comes from. The difficulty acts as a barrier to entry against a flood of low skill labor that will constantly undercut you (both in regards to age and income). Master a high value, higher barrier to entry language or two and you can write a six figure ticket for the rest of your adult life. And as certain languages begin to themselves age off, the demand often only goes up for the dwindling supply of engineers that still know it well.
- deleted 8y ago[deleted]
- jpindar 8y agoAny examples of those languages?
- rohansingh 8y agoI almost agree with the poster above, but I think it's less about the languages than high-value skills or specializations. As long as you're defining yourself by a language, you're more limited than someone who's known for expertise in some specialty. Examples include distributed systems, realtime software, embedded programming, network programming, etc.
- tluyben2 8y agoI feel my contribution is more in saving time by experience than anything purely programming language related. Instead of having ‘young people’ ‘iterate, move fast and break things’, I think up the basics and tell them that. It save stress not knowing what to do (in my opinion the iterating is just their way of figuring out what to do without that feeling you are wasting time; it is not a very efficient way as there is a limit on how fast you can iterate and in how many simultaneous areas) and less crappy software comes out as the iterating did not start in the completely wrong place.