I'm 30 and already there. My only option at the moment is going for project manager / CTO type roles, project manager roles I have no interest in and I have little desire to be the CTO of someone else's company unless I get to drive the vision of that company which is typically the CEO's role and joining another company where I'll be writing more of the same things I've been writing for the last 15 years hardly excites me.
I've started focussing on my own joint-ventures / startups as a means to get out of the rat-race, software development is no longer something that excites me to the point where I can't wait to get up to write code - it simply became a tool I use to build things and solve problems with. Seeing the big picture unfold still brings me joy (whereas the development process in the past used to bring me joy) - this does have the benefit that I can focus on extremely large projects and stick to it for very long. Maybe the next step for me is startup architect <- that excites me, maintaining someone else's code doesn't excite me. Solving complex problems still excites me, writing another login dialog and authentication system does not.
Furthermore I've seen the same cycles happen over and over again since I started programming day and night from age 15. Every year or two, something new comes along and everyone jumps on the hype wagon (I think it's called silver bullet syndrome), a few years later it gets abandoned for the next big thing. Some of these new things are truly revolutionary, others are just a different "syntax" to do the same thing, mostly I'm just seeing more of the same with different toppings.
Learning a new language is hardly a challenge anymore, as I've said before, most new languages are simply more of the same with different toppings.
I still have lots to learn, but unlike 15 years ago when it was a giant mountain to climb and climbing mountains was a fun thing to do (everything to learn), it has become a much smaller mountain to climb and there's less motivation to climb this smaller mountain unless it has immediate benefits. Example, learning Kotlin inside out has short-term benefits, I get to write less code and deliver more functionality, I see no benefit to learning Ruby (on Rails) since I won't be using it in any project anytime soon whereas 15 years ago, I would have learned it whether I was going to use it or not.
TLDR - be in the industry long enough, and you'll probably get to a point where you'll experience severe boredom, your payscale will probably start crawling towards its ceiling which further limits your options (unless taking a pay cut is an option) and your only further options are going into positions where you'll deal less with code.