The trick of course is to manage them through that. And that requires both trust and good communication. Trust to know that you will get there, communication to see how things work (from both sides) and be able to match up skills with trends.
Things at my current employer are changing (tech stack; from open source development to Oracle packaged software). It was time to get out. And it was hard. I got told by one company I interviewed with that even after having an in-person interview that I thought went well, they didn't want to proceed because they did not think I would fit "in a dynamic environment." Which was crap.
Fortunately, I found a place that respects the skill set that those last 2 positions helped me build up. Looking forward to the new opportunity.
In software - It's highly desirable for an engineer to be adaptable - Changing companies is a good way to expose yourself to different environments/perspectives (and therefore become adaptable). It's hard to get the same range of experiences from a single company.
This is especially true if you want to become a technical manager/lead (or CTO/CIO) - You need to be exposed to different approaches so that you know what works and what doesn't. You need to have a clear picture of what constitutes a good engineering culture vs a bad one.
You reference a 1:1 ratio between engineers in one role and engineers moving around. Based only on my experience I would estimate that ratio closer to 5:1.
We also had a third category, who were the engineers that worked in support activities like manufacturing and failure analysis. They might have the same "job" for years on end, but the job itself changed constantly.
Being able to build a career moving between projects in a large firm, where your reputation is always right next to you, would be quite a bit more challenging for the mediocre developer.
I think that's interesting, because I was recently involved in a hiring process where we had the opposite view - long tenure was a hint that if we could provide the right environment, that person was likely to stay with us for many years.
Long tenures can indicate loyalty and good performance, but it could also indicate other situations. Perhaps they couldn't get interviews or job offers from other firms. Maybe they got comfortable and found a place that wasn't too challenging. It could show someone that is risk averse (any job change has risk), or who is non-entrepreneurial. People who are overcompensated also tend to stick around.
Point being that it's obvious he's over 50 and also obvious he's a coding badass.
Staying up to date (at least aware, if not proficient) should always be a job requirement, whether you are a new grad or industry veteran.
I know many 50+ programmers who are doing quite well (monetarily, respect, responsibility, balance). Some independent consultants, some at startups, some with big firms, etc. A fairly wide variety. Not all had to go to management - in fact, I'd say most of the ones I know didn't.
The one trend I've seen is that older engineers that ended up staying with a single employer for the longest (say 10+ years in one job) generally have the most difficulty finding new work when the time comes.
There could be a few explanations for this. One could simply be that people who work for one company for a long time may have a smaller network. That could make job hunting more difficult. Another could be the whole "ten years of experience or one year ten times" cliche.
I do believe there is often some bias against candidates who had extraordinarily long tenures at one company, which may be associated with the thought that these candidates may either be too comfortable at their current job (not need to learn) or so ingrained in a particular work culture that other companies fear that they will not be able to adapt.