Likewise, some of the "kids these days" (literally what I call the rest of my much younger development team, and they're just as capable about poking me about my age :)) may be doing that in tech in their early-ish careers. I think it'd be underestimating younger devs to apply that too broadly, because I've seen too many little gems of genius from younger devs.
The way I see my role leading a younger team is to help the folks somewhat younger than me learn from some of the lessons I have learned: to spot code that is going to be a nightmare in the long run, to maybe gain my weird knack of being able to tell people what their bug is without even seeing the code. But they also have a valuable role in teaching me to be less conservative (disposition, not politics) when I should not be, or coming up with brilliant solutions that I was blind to.
If I had a point, it's that there's room in the world for all of us, and that both the old motherfuckers and the Kids These Days have a lot to bring to the table to build up each other. I hope this was useful in some way. :)
To be honest, i'm never usually that impressed with people that are in their mid-20s and working as developers. They can typically produce good output, but in my experience they are unable to state 'why' something works well. They're following best practices laid down by people in their 40s/50s years ago. I think they have the energy to not give up and trawl the forums till they get the answer, not necessarily finding the answer by considering the principles underlying the task