I’d make the case that it’s better to hire the 27-year-old because he is still at the stage of his career where he enjoys the stuff and is therefore more motivated to learn and work harder, while the 60-year-old is surely bitter about the fact that he’s getting paid less than the younger programmers. No one wants a bitter employee.
This assumes that the 60-year-old programmer has even learned .NET programming
This article is utter trash for that statement alone, what a blatant piece of age discrimination. If most 60 year olds learned COBOL then many will sunset with COBOL, those that do stay relevant with the newest technologies are exactly the type of developers who a smart person would want to hire. The reason being, that algorithms don't change, math does not change and also we have a dirty little secret that we keep reinventing the wheel on new stacks. So a 60 year old that has been through 3-4 stacks is going to have seen a lot more problems and solved a lot more problems that mirror problems that his organization is going to experience. They are also going to have mastered and learned a lot more foundational stuff. To assume that all programming knowledge is temporal is to stack the decks in favor of a certain viewpoint and ignores reality. Arguing that said 60 year old will be bitter is just a cop-out for lack of any sound argument.
I don't think the author means to justify age discrimination so much as to use it to underscore a point, which is that programming knowledge is something that takes (on the order of) 5 years to acquire rather than 40 years to acquire. Whether this is true, I am not sure. I don't really have enough experience to justify making any claims like that.
I think what he's really saying, to make an analogy, is that a programmer is more like a black smith than like an alchemist. A blacksmith is concerned with his tools and his technique, an alchemist is on a search for truth (or permanence or glory). Now he's also saying that being a blacksmith sort of sucks: your tools get old, you are smelly, it probably hurts more to pound your anvil when you're 50 than when you're 22, etc. Whether you believe that depends on your taste, whether you care about creating a good product or embarking on a potentially (very likely) fruitless search for truth.
This assumes that the 60-year-old programmer has even learned .NET programming
This article is utter trash for that statement alone, what a blatant piece of age discrimination. If most 60 year olds learned COBOL then many will sunset with COBOL, those that do stay relevant with the newest technologies are exactly the type of developers who a smart person would want to hire. The reason being, that algorithms don't change, math does not change and also we have a dirty little secret that we keep reinventing the wheel on new stacks. So a 60 year old that has been through 3-4 stacks is going to have seen a lot more problems and solved a lot more problems that mirror problems that his organization is going to experience. They are also going to have mastered and learned a lot more foundational stuff. To assume that all programming knowledge is temporal is to stack the decks in favor of a certain viewpoint and ignores reality. Arguing that said 60 year old will be bitter is just a cop-out for lack of any sound argument.