You're viewing a single thread.
When writing software that will be deployed to a production environment, it's better to slow down and take the time needed to write a higher quality, more durable solution than to rush and quickly kick a product out the door.
I don't know why this is a hot take, but sometimes it feels like it is.
Even better is to ship small increments often.
Unfortunately in many organisations, leadership doesn't really understand that instead of reducing quality, scope should be reduced in order to ship faster. And developers rarely have a say in these things.
While I agree that it can be considered a hot take industry wide, I don't think for most devs that is a hot take, the ones whom I've seen ship broken stuff were rushed on tight deadlines and didn't have the experience/motivation/political capital to fight back on deadlines.
It's a hot take because managers won't let us :'(