A third reason is the basic human's inclination towards certainty, similarity rather than risk, unknown--which might not have anything to do with prioritization and time-saving.

Someone might use calcultor rather than learning how to use spreadsheet, partly because he knows more or less for sure how much time it will take him to finish the job with a calculator, compared to spreadsheet he's not similar with.

This name/fame/reputation-based mentality certainly extends to programming. Many people were attracted to Java and OOP by their reputation. A downside is, of course, many people blindly fit their problems into a famed methodology or tool inappropriately.

This reminded me of the battle that some people really tried to prove Shakespeare was not Shakepeare, apparently due to the lack of evidence of his formal education. One of the most idiotic "proofs" of certain someone was Shakespeare was if you randomly pick a sentence from the writing of that certain someone, you can't tell if the sentence was or was not Shakespeare's. It's like saying this guy is the same person as that girl because you can't tell the different from the pictures of their lips.

That's pretty much the same backward justification process some people use to retrospectively justify the use of certain brand name product or famed method by famed consultant. Associating yourself with someone or something well-known (even if hollow) rather than nameless virtuous is another inclination many people has. That's simply a self-righteousness factor.

This basically brings us back in a full circle to what has been discussed a couple of times lately, know what we don't know or how we learn.