As I've gotten older my time has gone from '20% think about it - 80% code it', to '80% think about it - 20% code it'.
I currently work with a surprisingly well balanced spectrum of developers at my current employer. The median age is in the early 30s, with probably a third of us 40 and older out of 150 developers.
I'd say with some confidence, that the older developers in my company complete as many "tasks" but write less code when doing it, with a lower defect rate.
That 80/20 split (for younger me) is what taught me enough that I can now think it all out ahead of time. When I just started around 20 years ago, it was all new, it was all confusing, and all the answers were hidden behind obscurity, gatekeeping, and strange social norms (no StackOverflow back then). So I had to learn by brute force, smashing my face into every project for somewhere around 100 hours a week.
Now I have some knowledge and perspective, even the ability to pick out the fads and novelties from time to time. I can try new things on small projects and I can go with tried and true for the big things and I tend to understand which projects are better for which approach. I can visualize the data, the models, the inputs and outputs, and think through the logic from beginning to end, all within about 30-50 hours per week. That took lots of late nights and a ton of trial and error.
There's a good place for the less experienced and more experienced on any well balanced team, to be certain.
As I've gotten older my time has gone from '20% think about it - 80% code it', to '80% think about it - 20% code it'.
I currently work with a surprisingly well balanced spectrum of developers at my current employer. The median age is in the early 30s, with probably a third of us 40 and older out of 150 developers.
I'd say with some confidence, that the older developers in my company complete as many "tasks" but write less code when doing it, with a lower defect rate.