In JavaScript world the name of the game was always hiring and firing. Application quality, security, performance, accessibility and other things are largely irrelevant until someone gets sued.
What’s interesting is that the result is immature developers. This becomes evident in that although the goal is rapid hiring/firing, which is completely hostile to the developer, the impacted developer is somehow convinced such hostility is their primary vector of empowerment. For example if an employer mandates use of a tool to lower barrier of entry to less qualified candidates those less qualified candidates are likely to believe that tool is there primarily to benefit them. That makes sense if the given candidate is otherwise completely unqualified, but it’s nonetheless shortsighted and narcissistic.
As a result software quality degrades as the quality of people doing the work degrades while business requirements simultaneously increase in complexity/urgency to compensate.
That’s spot on - and it’s amplified by how the market rewards velocity signaling over craftsmanship.
Teams are optimized for output volume, not outcome quality. Hiring pipelines favor those who can “ship fast,” while the systems they ship into grow exponentially more complex. The result: shallow competence at scale.
AI just poured fuel on it - it lets everyone look 30% more productive while compounding the same underlying brittleness.