I think labor market incentives distort a lot of engineering decision-making especially at smaller companies, where the boss heard that React is hot and decides Solution X should be built with React.
Developers eager to develop their skills, increase their rates and advance in seniority end up focusing on the new hotness because of this.
Engineers who want to increase their impact and scope should focus first and foremost on the skill of making smart tradeoffs between technical realities and the requirements of other business functions--aside from simply writing code, this is what engineering is indispensable for.
Beyond that it pays to go deep in your mastery of a particular platform, the dependencies underlying it, and related technologies--all of these enhance your ability to design solutions.
Unfortunately the reality is there are very real financial incentives to keep jumping to the new hot thing every year.
I have recently started contracting in London, and this is 100% what I have found in my younger colleagues. Trying to do everything "the right way" without keeping in mind at all the business constraints has created a total reciprocal distrust with upper management - which in turn isn't at all able to explain how being able to do that makes you a much better developer for the real world, not for some fantasy world where time and resources are infinite.
* Ex-engineer managers pointing out that technology, then either brown-nosing or incompetent engineers running with it
* Tech debt: throw-away prototypes / experiments forced to production products
* Engineers padding their technical resume (probably intending to transfer before the debt is due)
* Engineers reusing existing knowledge instead of learning
* Premature engineering, small teams building for a big (hypothetical) future instead of building everything that comes in between
* Consultants / Contractors
* Low hiring bar
And plenty more. It's usually a systemic failure, with multiple parties failing to do what's best for the the customers and the business.
Usually I see the opposite. Engineers jumping on hot technology of the day (and making a half arsed job of it) rather than getting to know any one technology well.
It's worse than lazy, it's the new way of doing engineering that is glueing together ready made components.
I agree with the sibling comment of 'dcow'.
I will add a) innovation is a slow process and b) that a lot of projects take the _fast path_ of "fill-in-the-blanks" tools instead of thinking about a good solution.
To avoid speaking in vaccum, I will only cite 'Ansible' which is a tiny improvement over the previous hype. Obviously, if you consider the whole 'Ansible + Galaxy' there is value but still the wrong solution. All arguments I've seen for Ansible seem wrong to me.
AFAICT that time would have been better spent in functional devops approaches. My favorite being 'guix'. Also, I understand that Ansible galaxy was built by thousands of man hours by hundreds of contributors where a functional approach will require prolly more time and more focused effort.
Many cannot get to the grips that majority of work is just plumbing, yet another CRUD app or just plain maintenance.
So it is cooler to keep pushing for things like those companies, even if there is no need, after all the cv needs to match the new buzzword soup filter from HR.