Your comment is your perceived reality, and quite frankly it's wrong. If experience is a liability then the end-game of that line of thinking is there should be zero schooling or learning of any sort. If you're not learning everything from the ground up by yourself you're getting someone else's preconceived notions drilled into your head.
I'm sure you can see how this line of thinking leads to a total logical breakdown. The issue I think you are trying to illustrate oh-so-ineloquently is that a lot of developers ossify into "what they know". Then you end up in the "I have this one hammer and everything looks like a nail" issue that is actually real. Keeping up with current trends, tools and design patterns is definitely harder as you get older, but also one of the interesting parts of the job. For those who can't or won't adapt and learn, I'm sure there will be plenty of J2EE apps to maintain over the next few decades just like there are still Cobol apps to maintain now.
I'm sure you can see how this line of thinking leads to a total logical breakdown. The issue I think you are trying to illustrate oh-so-ineloquently is that a lot of developers ossify into "what they know". Then you end up in the "I have this one hammer and everything looks like a nail" issue that is actually real. Keeping up with current trends, tools and design patterns is definitely harder as you get older, but also one of the interesting parts of the job. For those who can't or won't adapt and learn, I'm sure there will be plenty of J2EE apps to maintain over the next few decades just like there are still Cobol apps to maintain now.