>Technology-wise, we no longer use engineering as a means to an end to solve a business problem. Instead, engineering became its own thing and most companies encourage and reward those who opt for over-engineered solutions, which means you spend more time fighting with dozens of layers of abstractions and chasing the latest JS framework instead of actually delivering functionality. This is mostly a symptom of the previous point where showing "growth" and bragging about your (over) engineering is more important than actual profit.

And yet, some kind of new and improved framework gets upvoted to the top of this website every week.

Seriously though, it truly disgusts and depresses me to browse Github and see projects which could have been accomplished with (literally) a single file being split into 10, 15, 20+ files, all wrapped up in some god-awful package managers.

No, developers; your JavaScript snippet does NOT need to be accompanied by two dozen .grunt, .yaml, .composer, .gulp, .jenkins, or .fellatio files.