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.
Comments
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.