I mean, if I do a quick search on the Danish job agents, no one is looking for someone who knows GraphQL. Yet I see people desperately trying to learn it in their free time because they are afraid of becoming obsolete.
I wonder where this fear comes from. It’s a fairly recent thing in my experience, and it’s not like it’s a buyers market. We still desperately need more developers.
If your reference point is these companies and their developers, then it can appear like you're getting more obsolete by the day, since they're always talking about the hottest new tech and you're seemingly not using it.
It's turned web development and software engineering into a game of keeping up with the joneses. And I suspect just like with social media as a whole, it's made a lot of people feel like they're inferior to the rest of the population/their peer group.
But I've got an article about that planned at some point. About how the Silicon Valley focused tech media and internet has given people the wrong impression about what most such work is like in most industries.
This is actually part of the reason we try to think about what technology we use and how we use it. We have too many critical systems and too few people, so we need to be extremely efficient in our choices. If something is cool, but adds complexity, then it’s just not worth it.
Because we are the public sector we do a lot of benchmarking though, and we actually have ASP WebForms legacy apps that are rated as high as your favourite mobile app by our citizens. Which was my point, your users don’t actually care about your tech-stack when it delivers.
Not because Vue/React/Angular aren’t nice, but because we don’t have to. If it doesn’t need to run offline, then a MVC framework with Ajax will do just fine, and they are extremely productive. Both because errors are server side, but also because asp mvc hasn’t really seen radical changes for almost a decade. We also rarely put things in containers, we don’t do automated CI/CD and we certainly don’t orchestrate things with Kubernetes. Not that there is anything wrong with doing that, but we’re not Netflix, we can publish a new build directly to an IIS during a slow period and no one will notice the service being gone for 5 seconds.
Sometimes I think it pays to do a little JOMO instead of all that FOMO. Especially if you don’t want to burn out. Changes are a constant in our business, but you need to make absolutely certain that adopting those changes make sense, and it has to make sense in the real world, not on hacker news. Our business doesn’t care one bit about the front-end tech stack, as long as it performs like they want it could be written in ASP webforms.