Hacker News new | comments | ask | show | jobs | submit login

> discrimination not truly based on age, but on stagnation

I can't speak in general, but I have observed in my circles that this is at least somewhat true, and for altogether natural reasons.

Most people, once they hit their late 30s or 40s, family (if they have one) takes priority and they don't have as much time to dedicate to going to Meetup groups, conferences or late nights spent gaining proficiency in new technologies. In general having kids vastly reduces one's free time.

Knowing a technology deeply requires many hours of intentional practice, commitment and energy, which many if not most people in that age range with families don't have a lot of at their disposal. Their "tech growth rate" slows down considerably relative to when they were in their 20s.

For example, I've noticed many SQL DBAs of a certain age have a hard time learning distributed databases because they often expect something familiar (databases are databases, right?) yet find themselves having to bone up on so many new concepts (that CS degree was so long ago) that many give up. Only the truly dedicated, truly passionate and truly nerdy persist, but they are in the minority. A common refrain heard is that "there's just too much new stuff coming out all the time, you can't learn everything", which is true, but it's often also an oft-employed excuse for not dedicating oneself to being current.

So when most average tech folks hit 50, they have pretty much lost about 1-1.5 decades of high-rate tech learning.




In my current job I see a LOT of what I call cookie-cutter J2EE developers apply for our open positions from big Wall Street banks.

I try to keep an open mind when interviewing these folks, and we even have some great employees with that background, but so very few of them surprise me positively.

I sincerely hope they get rescued from their dead end jobs some how. It's such a shame. So much talent just getting wasted (IMHO).


Good points, but also keep in mind that if your employer is giving you a steady diet of interesting projects using technologies that are highly relevant, you don't have any need to go home and do personal projects at night.

When I advise clients on career topics like this, I usually weigh whether the day job provides the client with a marketable skill set. If not, that person needs to consider doing things outside of work to maintain marketability. If the day job provides challenges and the proper set of tech, no real need to invest much additional time to learning.


> if your employer is giving you a steady diet of interesting projects using technologies that are highly relevant

Absolutely, and if they are not, one can either ask for them or switch jobs. The latter unfortunately is less of an option in smaller metro areas where the job market is limited. I've friends in smaller cities are who are stuck because there are only a few games in town.

That said, remote work is an option these days.

But there is still the inertia and difficult of switching jobs (an HN post a couple of days ago speaks to the difficulty in moving to a new tech job).




Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: