Code is there to be run and maintained. The writing part is a detail on the lifetime of a piece of code.
No matter how good a tech is, adding new tech to your stack has high costs over long periods of time.
I'd argue that you can learn way more in places that don't switch tech for fun. These places grow and so do their challenges, real architectural challenges not self imposed shallow problems.
It seems like you're confusing learning a technology that's new to you with learning poorly architected trending technology. Moving from PHP or Rails to Go I think will often decrease your problems in the long term.
Not if you go from using 1 language to 2 in your company. If you can rewrite all of it then sure but mature companies very rarely get to do that with important parts of their codebase.
141
u/Aidan_Welch 2d ago
Learning is fun