Programming is currently hating on OOP, in love with strong typing, and somewhere on the way from loving microservices to disowning ever to have spoken in their favor. Ten years ago, it was the opposite.
So this particular quirk of thinking in groups doesn't seem to be confined to the design domain. Nor do "swings of pendulum" preclude the pendulum also having some forward momentum in sum.
Think of it as a skier's waving, or a sailboat crossing against the wind, and the sideways motions is actually required for any forward motion to happen.
I totally agree. I call it "throw the baby out with the bathwater" syndrome. Usually some technology has a particular problem, probably not huge, but as that technology becomes dominant, its warts start to grate on more people.
So someone comes up with a new technology and says "Look! It fixes all the problems of Technology A!" And people who are new enough to the field who pretty much only have experience with Technology A think it's great, because this new thing fixes A's problems.
Meanwhile, though, Technology B has its own host of problems, and oftentimes those kinds of problems are the ones Technology A was originally created to fix! And so the pendulum swings until you get enough years behind you on Technology B where it's problems become apparent enough, so someone comes up with Technology C, which is basically Technology A with more modern trappings.
Whenever you make a technology switch, be very cognizant about what you're losing as well as what you're gaining.
Some of the things you mentioned are pure aesthetics - and they change with time - forward and backward. Some others change with the advent of tools and other developments. Micro services are hard to do right and they have been hard. But people rushed into it. With better tools in the future that might change.
Same with beginner/new projects embracing dynamic programming. It’s perfect for a new code add. It bites only later; when the enthusiasm has died off and you got to keep the codebase and tests up to date and things start slipping here and there.
Go is a darling now because it’s constraining. It skipped passed the last three decades of advancement in languages like they never happened. And then as it becomes way more popular people will ask for the same set of features that other languages have had forever.
And yet, things don’t have to change at an indigestible rate. Windows, for example, is changing so fast lately, that directions for use change on a semi-annual basis, and self-consistency is almost entirely gone. They never release a finished product, and It creates highly unnecessary cognitive burden.
So this particular quirk of thinking in groups doesn't seem to be confined to the design domain. Nor do "swings of pendulum" preclude the pendulum also having some forward momentum in sum.
Think of it as a skier's waving, or a sailboat crossing against the wind, and the sideways motions is actually required for any forward motion to happen.