As someone almost ten years older that has been basically in the same position, I think you have to challenge yourself sufficiently to grow if your job itself w

As someone almost ten years older that has been basically in the same position, I think you have to challenge yourself sufficiently to grow if your job itself won't challenge you appropriately. If your organization is too uncaring to change, life is too short to deal with bad jobs. But it is always worth working towards skills that will get you a better job. That is, do the minimum to say employed but put the real focus into getting to a saner, smarter company. I say appropriate because to me the whole point of modern devops is about having the entire organization work smarter, not harder, and together on the right things to be able to stay sane. Where I am, I know that the wider organization is completely not capable of actually fixing itself (when your network team is still manually running ping and tcproute instead of having monitoring galore from every link to another either with vendor tools or something crude like Nagios, you're too far behind to ever catch up). So, even if my corner of the devops world is completely flawless, I will be basically handing off tickets to another team 100% of the time while my applications that depend upon them suffer the consequences. According to my boss I already am changing how others do things by showing the power of solid, modern tooling and instrumentation but it's awful hard to tell that any of it makes a difference when you're doing 20-hour days 3 days in a row all for issues you only diagnosed, none that you are directly responsible for.