A related question for you OP -- I'm at a similar age, with a dev background, but have reached the point where my accrued experience does not allow me to dutifu

A related question for you OP -- I'm at a similar age, with a dev background, but have reached the point where my accrued experience does not allow me to dutifully perform as a senior developer anymore. The Big Picture beckons, biz dev / solution design / architecture all overlap in my responsibilities, and while work remains interesting, it seems that somehow my increased ability narrows my options. I've considered the PM route, but the horror stories hold me back. How do you find this "knitting together" working out in the long term? I'm with you on the "the damn ground is moving too fast" sentiment. My back-end of choice is Erlang-based, because in relative terms it's grounded in immovable bedrock, they fixed all the bugs decades ago and Things Are Not Changing. All my FE libraries are deliberately chosen versions and there is no ever-churning build chain to trigger a cascade of breaking updates. While this approach has worked for me well so far, I can tell not that many others appreciate it. How do you teach the value of reliable constancy to people enamoured with relentless change and tools for tools' sake?