I'm old enough to have seen this as a fashion trend unto itself. If you go back and watch TV shows from the 80s, you'll see a lot of 50s nostalgia. In the 90s

I'm old enough to have seen this as a fashion trend unto itself. If you go back and watch TV shows from the 80s, you'll see a lot of 50s nostalgia. In the 90s, it was the 60s that was being fetishized. They even brought back Woodstock, twice. I was in high school in the 90s and "hippie fashion" was very popular. Tie dyed shirts came back etc. In the 2000s the 70s were in. We had TV shows like That 70s Show etc. Then it was the 80s, and now 90s nostalgia is starting to come in. It's the cycle of aging. All the kids and teenagers from those decades are now middle aged and they want to consume nostalgia. If they had kids in their 20s, then those kids are now teenagers and young adults and are becoming curious about their parents lived experiences and all the things that they just missed out on (during the 00s I was very interested in the 70s since that decade happened right before I was born). But this is a specific exception, not the rule. Middle aged consumers are not the trend-setting hipsters who create new fashion trends (the stuff that they will fetishize when they are middle age). What's really ironic, though, is that in tech there really isn't much that is new. Even AI/ML was being researched as far back as the 1940s, we had working proof of concepts in the 80s. We knew how to do this stuff ages ago, and had practical applications. We just needed the hardware and data accessibility to catch up so that we have the storage and computing to actually train these things. Every advancement over the last 20 years has been small incremental refinements. The big stuff is not new. But the industry still fetishizes it like it's new. "Cloud" is just resource sharing. We're back to mainframes, complete with the vendor lock-in caused by proprietary APIs. And yet it is branded, marketed and fetishized as if it's "new." OOP is soooo passe. We tried that in the 90s and 00s and there were ... gasp... problems! People wrote buggy and difficult to maintain code. Enter Functional Programming and now this is the way that we do things. It's impossible to write bad code in this paradigm ... right?! Relational databases are slow and complicated and require DBAs to maintain. In comes NoSQL and key/value doc-stores ... now THIS is the way we do things. You can't develop a bad product using a doc store database ... right?! Restful APIs require strong collaboration between backend and frontend developers and simple, single-purpose contracts aren't very flexible. In comes GraphQL now ALL web apps need to use it because you can't develop a difficult to maintain application using GraphQL .. .right!? This is the point of the article and after 25 years in the industry I have a hard time finding the lie.