Do you mean that perspectives change into the 40s and 50s?

I find that I'm considering this much more now that I'm in my 40s, because I know that as a generalist developer, I will be slowing down in skills compared to the younger devs, so I need to make sure my career is developing in areas that value my experience and soft skills.

I think it's even easier to get complacent with not challenging those soft skills and "tech wisdom" by staying too long in one role.

>Do you mean that perspectives change into the 40s and 50s?

You may still want to try new roles or at least take on new projects where you can learn new things.

But...

I find the older devs I know (I'm not actually one myself) mentoring, managing, possibly speaking in public more than they do just writing code.

And, especially as people get into their 50s, at a larger company that's doing reasonably well, there's nothing wrong with seeking out a comfortable position that plays to your strengths.

I already feel this slowdown and I'm barely into my 30s.

Very true. As I grow older I realize that one should take the authors age in consideration when reading articles like this should be read.

The problem is you need to read the article to find out the author is...young. Perhaps they assume that the title screens out those of a certain depth of experience. Like misspellings in Nigerian scam emails...