It just lays more bare what the people up top care about. Most devs eventually learn this but they are often somewhat insulated as they are left to their own devices to build a product via a given framework or standard. But the C-suite has never cared about code quality or security unless a big customer or investor cares about it. The C-suite is focused on making money, especially through disciplining labor. They are very happy with the worst thing you've ever seen so long as it appears to function and neither big customers nor investors are complaining about it. Tech is usually treated as a cost center, it is something to minimize and fulfills a purpose that they would rather contract out.

These are folks with big egos and little education so they also think they know enough about the topic to manipulate their workers and discipline as needed. This has never been a problem for them before except when it comes to tech and how much they have to pay their workers, as there is limited supply. They are now having a great time attempting discipline that was otherwise difficult for them to achieve, so this is a double-whammy of standard labor discipline plus scratching a long-held itch in profit maximization. It doesn't even have to work, it just has to fulfill those basic criteria from earlier.

In large part this is because there is a substantial disconnect between production and profit, the actual product being sold and how money is made is often two or three degrees removed from "we made $x sales and had $y costs" that the C-suite can just tank four companies in a row and still make out like bandits - so long as they please the big customers and investors.