4 ms·

I don't think it's that bad. I've never heard of someone who got fired because they didn't know the latest JS framework. Also, new tech trends are not just hot

I don't think it's that bad. I've never heard of someone who got fired because they didn't know the latest JS framework. Also, new tech trends are not just hot air, there's also a lot of innovation happening. You just have to see through the hype and wait until the dust settles.

zerkten 7y ago
There is also the situation that someone gets hired for their tech skills, but the thing that keeps them in a job is their ability to pick up the domain. The tech choices are often point in time decisions which are irrelevant to any outcome. The domain knowledge builds is worth more than any framework knowledge. If you are successfully (i.e. the business or product keeps being developed) you still need to be aware of the internal weaknesses of your original choices and the external opportunities of updating to something more modern. The challenge is in managing the transition which is a skill in itself.
Rychard 7y ago
> I've never heard of someone who got fired because they didn't know the latest JS framework. Sure, but I've worked with a number of individuals who have either resigned (on their own), or have been let go, solely because they had no desire or interest in keeping up with their craft. I think that's effectively the same thing, though. Ultimately, the notion of not wanting to stay abreast of the current industry trends is neither something I can relate to, nor is it something I see as being compatible with one's employability.
mcguire 7y ago
How many haven't been hired because they didn't know the latest JS framework? Reinventing wheels isn't innovation, particularly if the reinvention isn't round.
FpUser 7y ago
If we are talking client side JS I think they're just trying to solve the problems that desktop had solved ages ago. And they keep smashing heads in a process.

4 ms·

I don't think it's that bad. I've never heard of someone who got fired because they didn't know the latest JS framework. Also, new tech trends are not just hot

by blauditore 7y ago

zerkten 7y ago
There is also the situation that someone gets hired for their tech skills, but the thing that keeps them in a job is their ability to pick up the domain. The tech choices are often point in time decisions which are irrelevant to any outcome. The domain knowledge builds is worth more than any framework knowledge. If you are successfully (i.e. the business or product keeps being developed) you still need to be aware of the internal weaknesses of your original choices and the external opportunities of updating to something more modern. The challenge is in managing the transition which is a skill in itself.
Rychard 7y ago
> I've never heard of someone who got fired because they didn't know the latest JS framework. Sure, but I've worked with a number of individuals who have either resigned (on their own), or have been let go, solely because they had no desire or interest in keeping up with their craft. I think that's effectively the same thing, though. Ultimately, the notion of not wanting to stay abreast of the current industry trends is neither something I can relate to, nor is it something I see as being compatible with one's employability.
mcguire 7y ago
How many haven't been hired because they didn't know the latest JS framework? Reinventing wheels isn't innovation, particularly if the reinvention isn't round.
FpUser 7y ago
If we are talking client side JS I think they're just trying to solve the problems that desktop had solved ages ago. And they keep smashing heads in a process.