My younger and naive self used to over value the tech stack of a company, nowadays I don't care, there's way more important issues than the specific tech stack chosen like people, organization and processes.
A strong engineering team pushes for meaningful and well organized requirements collection and encoding, documentation of the business domain, values (meaningful) testing and is strongly oriented towards providing the best developer experience possible.
Languages and libraries do play a part in developer experience and satisfaction, but they are generally way less important.
If I'm a Go developer, or changing jobs because I want to use Go, of course that it is in both mine and my future employer's best interest to set expectations if I'm gonna work on Go or on ASP.NET.
"sure milansm, you'll work on Go code. we just need to support this ASP.NET codebase for a little bit and then you can lead our migration to Go. I promise.".
In this market, employers are saying anything to get folks in the door. They're scrambling for workers, and a lot of times it's because their codebase is shit and folks are leaving in droves, so they dangle carrots to get folks to support their decaying crap.
My younger and naive self used to over value the tech stack of a company, nowadays I don't care, there's way more important issues than the specific tech stack chosen like people, organization and processes.
A strong engineering team pushes for meaningful and well organized requirements collection and encoding, documentation of the business domain, values (meaningful) testing and is strongly oriented towards providing the best developer experience possible.
Languages and libraries do play a part in developer experience and satisfaction, but they are generally way less important.