I feel like there's a decent middle-ground there, though. You don't have to sit down for two weeks and architect everything, but I feel like you should have indexes on your database columns.
Yeah, I personally like to think code quality doesn’t matter too much because you can refactor / rewrite fairly easily later. The same is not true for your data model: bad data will live with you forever and it’s much, much harder to refactor.
Eh, you can migrate bad data to a better model, too - and you can write code in such a way that you paint yourself into a corner that makes rewrites, especially incremental rewrites, very difficult.
I just mostly think that all these issues are just people being bad at writing software, and that if you're bad enough at it, you can crater your business. If it's only a little bad, the business can limp along until you can rewrite it.
In practice when people do this, 99.9% of the time it leads to data continuity issues which makes the old data essentially unusable for most important things.