It's not the youngster who are jobless is the older software engineers who never learned to learn new concepts. The older programmer to so much time to learn everything from algorithms , to cryptography, and things that are analytical they forget about learning new technologies. Yoru comment shows why older people have difficult getting jobs. It took you a day to understand how a listview work while a good young programmer who understand technologies should be able to pick up any technology and understand it in a few weeks.
The parent was commenting on a broken framework, something that should be an anathema in any shipping product, and around spending (wasting) time determining that the API itself was faulty. Replacing the faulty API call took two hours.
But to follow onto to your point, it's also the case that the younger programmers can need a decade or more to make enough mistakes; to variously learn what the older programmers already know about various fundamentals of the programming and product-creation business.
And to extend your point, it's been my experience that having a team of younger programmers is just as big a headache and as big a mistake as having a team comprised entirely of older programmers. A mix works better, as the younger folks teach the older folks and they bring knowledge of new technologies and volumes of enthusiasm, and the older folks can teach the younger programmers about temperance, testing, productization and business in general.
Not so much, mostly people keep reinventing the wheel over and over again.
Consider, there is vary little that separates handheld Apps from desktop applications. Sure, if you come from the Web side of things it seems new and nifty but they are just stand alone applications. Capacitive sensing touch screens where where new in 1965, but wait it's 2012. http://www.billbuxton.com/multitouchOverview.html
People worry about what happens when desktop CPU's have hundreds of cores, but the super computer world is already dealing with hundreds of thousands of cores etc.
PS: I think this relates to the hacker mentality. If you find a problem you look for a solution rater than see how other people solved the same problem 30 years ago.
Since the 70s, most apps have comprised "forms" (screens for a user to enter something, that will be stored in a database) and "reports" (screen that nicely format the contents of a database). This is all Facebook et al really are...
A loop is a loop. Math doesn't change much either. Nor does the concept of space and time, etc. It seems new and different to young people, but underneath, it's mostly the same as it was 40 years ago.
> Yoru comment shows why older people have difficult getting jobs.
You make several assumptions about him that don't seem supported, but worse why make this personal?
> It took you a day to understand how a listview work while a good young programmer who understand technologies should be able to pick up any technology and understand it in a few weeks.
So, older people don't get jobs because it takes them a day to pick up what a young programmer can understand in a "few weeks"? Really?
I think he meant it only takes them a "few weeks" to understand a whole technology (e.g the entire Android API rather than the listview).
I think part of the reason you can feel like you are learning faster when you are younger is because you look at everything enthusiastically and hammer through your education seeking out the juicy good bits of a technology and kind of glossing over everything else.
As I get older I find myself evaluating things much more slowly and cynically, checking under every rock for things that can bite me in the ass.
