Earlier quoted context omitted.
I agree. I have to really fight people when I try to write robust software. "Why are you writing a proper parser when a hacky regex that I thought about for 2 seconds worked the one time I tested it? You're wasting time." They don't understand that I'm not wasting time, I'm just choosing to spend a little bit of time earlier, because I don't like spending a lot of time later when debugging why everything broke.
Same here. I stopped suggesting robustness because no one cares.
Shoddy code only happens in "the production is on actual fire, not manager-imagined fire" fixes and not for long.