While there can be a strategic value to just getting something working, the tough part is that many times that is used as a crutch to do no more thinking or design, quite possibly because they've never been called to. And refactors happen less than they ought to. The point is to be strategic about when to turn the quality/speed dial towards speed and know you are consciously taking on tech debt.
Some of the worst systems I've seen were those designed to "last for decades".
But that's also not the same as "to last decades". A lot of the old space code was used and dismissed after a few years / missions.
The key difference is not "future-proofing" but "proofing" in general: the code had to be absolutely robust.
I.e. basically everything non-web/non-mobile has a higher lifetime.
I personally think the author is to harsh on "tactical programming" (solving problems locally without the big picture in mind). I agree with someones note on HN that tactical programming is fine till you get a product market fit. Technical debt has not to be paid back if the product fails.
I try to design strategically for overall architecture and don't care for most of the rest (in worst case you can refactor later).
If 9 out of 10 startups fail you can have huge savings. If you have enough success that it matters then you have the resources to improve.