Depending on why code cannot be run locally this is a pretty big sign that the organization is a big mess. If you like that sort of thing, then there's a lot of

Depending on why code cannot be run locally this is a pretty big sign that the organization is a big mess. If you like that sort of thing, then there's a lot of fun and room for growth if you can start untangling the code. There's always going to be some grumpy old man in the corner who like things to stay the way they are, but many colleague will definitively appreciate you making they lives easier, and if you're good at it, then it's an easy productivity sell to management (unless management is completely fubar as well). Sadly it is the way at least parts of the industry is moving. You either get to work on remote VMs, in a container hell or live in production. The whole container stack gave a large number of businesses a way out of the limits VMs put on them, but now developers have mini-Kubernetes clusters running on their laptops and they either developer directly in containers or constantly rebuild. For some things there's just no way around it, you need the infrastructure to test your work, but for some everything just starts in a container. I partly blame complex build systems, bad package managers and poor coding practices that locks you to extremely specific versions of libraries or other software packages.