>Perhaps it might be better if younger programmers learned the old stuff instead of just badly reinventing the wheel every few years. That's pure gold. Not to

>Perhaps it might be better if younger programmers learned the old stuff instead of just badly reinventing the wheel every few years. That's pure gold. Not to say there haven't been advances--there certainly have been. But, there's also the issue of the shininess of new tech giving it undue cred, while simultaneously translating to an outsized denigration of the tech it purports to replace. Frankly, a lot of these problems have been solved, and solved well. Look at NoSQL as an example. There are certainly use cases for it, but then people went nuts, exclaiming things like "RDBMS must die" and touting no ACID transactions as a feature/benefit. Then, you get the trickle of reports that maybe NoSQL wasn't the best choice for this or that. Finally, fast-forward to 2018 and you have announcements from MongoDB that they now support ACID transactions. Many older coders have seen enough of these cycles, and have adopted a justifiably-cynical posture of "wait for it...".