Additionally, it is extremely frustrating working with enterprises neck deep in technical debt located in the middle of nowhere oftentimes with really poor tech

Additionally, it is extremely frustrating working with enterprises neck deep in technical debt located in the middle of nowhere oftentimes with really poor technical and organizational maturity teams trying to move into the cloud... in 2017. I've been doing the raindance of cloud migrations since 2009 and it's almost a net negative career path because instead of working on relatively new technology and concepts 60%+ of the time, you spend a lot of time working on long-outdated versions of everything, especially stacks that are in oversupply of labor or are so obscure you can't hire anymore (not a lot of Delphi folks out there despite its merits, sadly). So now to compete with peers not dealing with legacy as their literal job, I have to spend another 20+ hours / week to stay current with people who might actually work on somewhat modernized / greenfield systems that are just doing a 9-to-5 job and get paid maybe within a 15% gap. This is not the same thing as Javascript framework fatigue despite sounding like there's similar mechanics.