It's bad for building your resume. Managers and employees are rewarded for popular thing. Popularity is mostly a function of novelty. So the (social and therefore economic) incentive structure is inversely correlated with choosing boring technology.
It's bad for building your resume. Managers and employees are rewarded for popular thing. Popularity is mostly a function of novelty. So the (social and therefore economic) incentive structure is inversely correlated with choosing boring technology.
I see it as analogous to people are frequently rewarded for putting out the fire instead of preventing the fire.
Exactly. When I joined the company I'm at now (consumer energy industry), the energy crisis hit and the servers melted from all the people looking to fix their contracts etc. I wasn't directly involved, but loads of developers did a mammoth effort to rewrite old services to prevent this from ever happening again.
New energy crisis this year, the servers held, the company made a lot of money from new contracts via a combination of getting lucky with long-term buy-in contracts and the servers staying up unlike the competition. But there were no heroes, no praise to e.g. the developers putting in the extra hours, etc - it was business as usual, or business as it's supposed to be.
I've been noticing this as a solo dev. I need to put lots of work into infra and security, and all I get for it is... the thing not blowing up (hopefully!).
The work is invisible, and impossible to "show off", so it's a bit unrewarding and demoralizing. But hey, someone needs to do it!
And the worst part is, because it's invisible, a higher up manager will think "Ah, we don't need these people anymore, let's replace them with juniors, an external company, and/or AI". It's maddening.
It's why senior developers should end up in management or in positions of making decisions, but it's a completely different type of job to software development, where reason and objective truth and whatnot is barely relevant compared to social skills and connections. (this may be inaccurate, I'm not in that 'layer').
Exactly; I've seen a number of instances now of people pushing the hip new technology, but jumping ship (i.e. getting promoted, a new job, or a different assignment) shortly before or after the shiny new thing was "done".
In one case, ten years later, the company is still struggling to maintain their Scala applications in an environment where there's barely any Scala developers (and who charge a premium because it's specialist work), while the main author(s) went on to work at the company behind Scala itself. I'm sure Scala is great for specific use cases (just like every other non-top-10 language out there) but please, think very carefully before trying to build your company on top of it.
Try to explain that part of an imagined "Agentic AI Everything" product being built would be cheaper and more efficient as a simple function call. Good luck!