The problem arises when you realize that most of the kids are not so adept at, well, solving problems that arise.
I would say most programmers in general lack this ability.
As a corollary, that lack of experience is a basis for lack of creativity.
I think it is *possible* for experience to help creativity, but it seems more often than not it is used to hinder creativity. Why figure out a new way to do something if you already (think you) know the best way.
They only know what they were taught with perhaps a few limited ideas, and haven't enough hands-on time in the real world to realize that there are multiple ways to get something done, especially on a macro scale - many of those ways being far more efficient and elegant than what they just barely learned in school.
Depending on the school, the way they were taught in school may in fact be the current best way to solve a problem. I find stubborn older programmers are just as likely to latch on to their one way of doing things, and at least the new stubborn programmers will have latched onto a slightly more modern single solution.
Oh, and I have found that the kids by and large have little-to-no people skills. At all. In a company larger than 400-500 people, the ability to explain and persuade becomes just as important as the ability to do your job.
The only thing worse than the people skills of younger programmers is the people skills of older programmers.
So let's tie it all together: As the near-median mid-40's guy, I've found that I don't have to toss my life upon the altar of the Kanban board. Instead, I find ways of getting the work done more efficiently, and have the people skills to demand (and get) management to set realistic timelines to meet the company's goals (meanwhile, the kids just bitch, moan, then go blast out 80+ hour work-weeks to meet the deadline, often at cross-purposes which blows the timeline anyway - then someone else has to go back in and refactor their barely-running shit, usually after release).
I don't see old programmers being more efficient. I see good programmers being more efficient. And as I said before, I find the younger programmers to be much more humble even when the do in fact know all these things they just learned in school (often things older programmers who went to school a long time ago, or never went to school have never heard of). I find that younger programmers, especially the ones that are still dating still have an incentive to be able to relate to other people.
And yes, the young programmers don't have all the experience they need, but they are like sponges. They absorb information you give them. If you point them in the right direction, their limitless energy and enthusiasm is often more than I myself can muster.
We have lots of old bad programmers that we can;t even give busy work to because they feel it is beneath them. Or they just bitch and moan and take a really long time to do a half ass job. Then you put some new grad on the job, and they follow directions and finish the task in a fraction of the time
...and that my friend, is what an old fucker brings to the table. ;)
A *good* experienced programmer is invaluable. The problem is that most programmers are terrible. Young programmers are malleable. Old programmers are either really good, or more often they suck and can't change because are stubborn as well.