There was no more challenge in it. I could still learn new tech, but I wasn't learning anything new about myself an my abilities.
Even when it came to doing "new" stuff (which as you discover in time is often just repackaged old stuff), I already was 99.9% sure I would master it, and it was just a matter of time and hard work. That not only took away the challenge, but also made me less motivated than my younger coworkers for whom everything was shiny and new, and who didn't have the experience to always avoid obvious (to me at least) modes of failure.
Managing was a challenge I could actually fail at (and still do on a regular basis...).
Yeah, programming is still more "fun" to do than managing, but it now is the kind of fun I do as a hobby (as in, hacking in stuff that will never get finished), not a job. A dead end job for me is a job that offers no more real challenges, and a challenge for me includes the risk of failure.
(Of course one other key motivator was 20+ of experiencing how bad management can completely suck all fun and productivity out of programming.)
I also don't want a management position and plan a technological move. Are you happy with what you did?
The general idea was that as you progressed through your technical career, you would be making more and more important technical decisions, measured by the impact to the company.
A junior engineer would be making technical choices that affected one subsystem, a principal engineer might define a protocol between two large components, and an architect would be making technical decisions that affected the entire company.
You can always nitpick these things to death, but I liked the general idea.
There are many great things that a CIO can do without having to spend a lot of their time tracking things.
Also: Because he was a manager for a few years, that means that his technical skills were almost zero. So he wouldn't be able to be as agile in finding another position as he was as a developer.
I don't know where I see myself in 5 years, but it might actually be still just coding, no actual change in title or function. It's fun and challenging and I imagine it can be like that for a long time.
Instead, a dead end job for me would be caused by projects that are boring, or that the process has become overly bureaucratic, or that the company interests or culture have become too corporate or political.