3 ms·

You only need to be worried if your skillset is "deprecated", for example if your current position of 10 years consists of mostly Adobe Flash programming In fa

You only need to be worried if your skillset is "deprecated", for example if your current position of 10 years consists of mostly Adobe Flash programming In fact if your skills are applicable to the job market you are in much more demand than any 20 something year olds even if they have 5 years of experience with the same technologies

austin-cheney 3y ago
Not exactly. You also need to be aware if your field is dominated by young people or high insecurity. For example as a JavaScript developer my interests are almost entirely in systems automation with Node and building feature complete end user products. That is completely out of alignment with my peers and what the industry is looking to hire. The name of the game is tools, frameworks, and trends for putting text on screen in a web browser. When you are fresh in your career its all about the literacy of the experience as in how to write code and just delivering anything, but eventually you will grow out of that. When you grow out of that you need to make sure you are in a position where the expectations of your employment grow with you.
- schwartzworld 3y ago
  The fact that most JavaScript jobs are frontend isn't a problem with the community. You're writing the language that web UIs are built in, so there are a lot of those. And every time I look at the market, most of the new jobs seem to be in react, vue or angular, all three of which are old enough and mainstream enough to not be described as trends anymore. That said, a skill set like yours would be right at home on a large front end team. Most react developers don't really know how to get the most out of node. You need someone in the organization who really understands it. That layer is a blind spot for many, and it's a problem because front end involves a lot of tooling that needs to play right together, and more and more what we do is work I would have traditionally been considered backend.

austin-cheney 3y ago

Not exactly. You also need to be aware if your field is dominated by young people or high insecurity. For example as a JavaScript developer my interests are almost entirely in systems automation with Node and building feature complete end user products. That is completely out of alignment with my peers and what the industry is looking to hire. The name of the game is tools, frameworks, and trends for putting text on screen in a web browser. When you are fresh in your career its all about the literacy of the experience as in how to write code and just delivering anything, but eventually you will grow out of that. When you grow out of that you need to make sure you are in a position where the expectations of your employment grow with you.

schwartzworld 3y ago
The fact that most JavaScript jobs are frontend isn't a problem with the community. You're writing the language that web UIs are built in, so there are a lot of those. And every time I look at the market, most of the new jobs seem to be in react, vue or angular, all three of which are old enough and mainstream enough to not be described as trends anymore. That said, a skill set like yours would be right at home on a large front end team. Most react developers don't really know how to get the most out of node. You need someone in the organization who really understands it. That layer is a blind spot for many, and it's a problem because front end involves a lot of tooling that needs to play right together, and more and more what we do is work I would have traditionally been considered backend.