If we dropped every new feature today and just focused on tech debt, it would take us months to catch up. But in the meantime, the show must go on, so we just continue accumulating debt. Nobody in engineering, nobody in sales or product management even has the power to stop the madness - this is all driven from the customers. And it gets worse if you are a b2c business or provide services to a government or two - you just don’t have much wiggle room.
Countering my Gell-Mann amnesia here (many times I read about my area of expertise I see snappy criticisms trickle into the mainstream when the reality on the ground has long moved ahead and the supposedly insightful HN criticisms are cliches being routinely addressed within the expert circles, think "deep learning is just X, it doesn't address Y!" or "physicists are obviously boneheaded and got stuck at assumption Z!").
So, with the above in mind, I wonder if Google is actively countering this. If random people know this as a stereotype (and I read this often, and hear it as a stereotype of Google also in real life), then perhaps leadership is even more aware and either decides not to change or has already implemented things they think would help. Any current Googlers to chip in?
Product wants new features and new products, and they want them now. Sales wants new features and new products, and they want them yesterday. Finance people want everything to be cheap, but since most engineers have no idea how to prove to them with actual hard data that it's cheaper in the long run ship features more carefully and slowly, and build things with reliability and robustness in mind, finance people go in the opposite direction and think that hiring inexperienced developers from the cheapest places on the planet is the way to go, because "cost of R&D per head" is a very easy number to quantify.
Unfortunately very few companies have an engineering department that can overrule all of product, sales, and finance. In general even one of those three being stronger means engineering never has the buy-in to take the time to do things the right way. And if you're the engineer who consistently pushes back product and feature releases because you want things built correctly, you get fired, or at best marginalized.
Interesting that you mention Google, since it has a reputation for being more engineering-focused that most companies. From what I read on HN (perhaps not a representative sample, but...), it seems like Google has a culture of "build something cool to get promoted and then stop caring about what you built because maintenance doesn't get you promoted any further". If true, I think that very easily explains Google's "hot messes".