The reason I stopped coding is that I got into it to solve problems, but I got tired of spending what felt like 90% of my time writing unit tests, wrestling with frameworks, and solving problems with upgrades to the huge webs of dependencies for even basic projects. In other words, I got fed up with what coding has become. It's no longer hacking. It's toolchain management.
I'd always been a full stack developer, so I just started focusing more on the sysadmin side and gradually transitioned over there. I can manage toolchains just fine if I want to focus on that. My coding experience is handy when we're trying to troubleshoot a bug that only shows up on production ... uncommon, because our dev and QA groups are GREAT, but it still happens. I not only know where all the logs are, but I'm able to read the code and make sense of stack traces from the different languages we use.
Those who think what I've done is ridiculous don't understand how scripted everything that happens in the sysadmin world these days. Everything in infrastructure/operations is scripted except the troubleshooting -- and even that stuff gets scripted as soon as it's done so that it doesn't pop up again. Yes, the native language of these tasks is bash, but ruby and python are becoming really popular. So's haskell, for those who can speak it. What's disappointing me right now is that all of the chef stuff we're doing is starting to get complicated enough to have a big toolchain (thankfully managed right now with bundler) and starting to grow unit tests... Didn't I make a career change to get away from this crap?
I think I'll go be a DBA next. ;)