4 ms·

I personally find that most developers (especially those in a web related field) tend to shift to newer technologies when there is very little reason to do so,

I personally find that most developers (especially those in a web related field) tend to shift to newer technologies when there is very little reason to do so, and perhaps more importantly, be an evangelical today. Ask yourself this: do you seriously think that a company would benefit from switching stacks every few years, or sticking with a mature and battletested technology?

ratww 4y ago
I find that this happens mostly due to career expectations. Gotta stay up to date to get the recruiters chasing you. But when everyone else is also up to date, gotta stay ahead and be an influencer/evangelist. > Ask yourself this: do you seriously think that a company would benefit from switching stacks every few years, or sticking with a mature and battletested technology? In my experience this is unfortunately situational, and depends heavily on who's answering. Someone who loves the current stack will say "don't change it". Someone who loves the next stack will say "yes burn it to the ground". Both of them, after doing a bit more self-reflection, will probably say "well, it depends, but probably not".
zero_shift 4y ago
I personally find that folk online who accuse "web developers" of neophilia over-estimate the amount of change in webdev and show little interest in the motives behind new practices. For instance, calling React "yet another new framework" when it's eight years old. Or loudly opining "why does everyone want to stop writing traditional CSS? These JS programmers are idiots" rather than pausing to reflect that, actually, CSS might actually have a bad reputation for a reason.
- marcosdumay 4y ago
  > CSS might actually have a bad reputation for a reason Hum... You mean people that hate CSS but somehow love JS? I don't think I trust their judgement.

4 ms·

I personally find that most developers (especially those in a web related field) tend to shift to newer technologies when there is very little reason to do so,

by subtra3t 4y ago

ratww 4y ago
I find that this happens mostly due to career expectations. Gotta stay up to date to get the recruiters chasing you. But when everyone else is also up to date, gotta stay ahead and be an influencer/evangelist. > Ask yourself this: do you seriously think that a company would benefit from switching stacks every few years, or sticking with a mature and battletested technology? In my experience this is unfortunately situational, and depends heavily on who's answering. Someone who loves the current stack will say "don't change it". Someone who loves the next stack will say "yes burn it to the ground". Both of them, after doing a bit more self-reflection, will probably say "well, it depends, but probably not".
zero_shift 4y ago
I personally find that folk online who accuse "web developers" of neophilia over-estimate the amount of change in webdev and show little interest in the motives behind new practices. For instance, calling React "yet another new framework" when it's eight years old. Or loudly opining "why does everyone want to stop writing traditional CSS? These JS programmers are idiots" rather than pausing to reflect that, actually, CSS might actually have a bad reputation for a reason.
- marcosdumay 4y ago
  > CSS might actually have a bad reputation for a reason Hum... You mean people that hate CSS but somehow love JS? I don't think I trust their judgement.