Maybe unpopular opinion: Either do the same or leave if you cannot handle it. What you're running into is mismatched incentives. Why would they even care about

Maybe unpopular opinion: Either do the same or leave if you cannot handle it. What you're running into is mismatched incentives. Why would they even care about making the code nicer? It has mostly downsides. So the company can move faster? They don't care because they still get paid the same. It's not their company. Refactoring takes time and doesn't show up on most performance reviews. It's the gmail affect - you get promoted when you ship new features and make a "new version of something" - not by fixing old code. Cleaning up code also has the downside that the original authors are now replaceable because more people can understand it. By trying to change this you are probably just hurting yourself. You are making enemies and annoying people and are not benefitting anyone. This is pretty common in FAANG, but it's not like this in all teams. It depends on the team more than the company. There are some teams that are more "startup-like" where incentives are a bit more aligned. Maybe you can transfer.