I have a request for opinions! I’ve noticed that software quality never seems to enter into conversations about scaling. Do code hygenie, writing clean code, a

I have a request for opinions! I’ve noticed that software quality never seems to enter into conversations about scaling. Do code hygenie, writing clean code, and good documentation not matter when you’re moving fast and growing like crazy? I’ve noticed the approach seems to be to focus on operations rather than the way the code is written. Use CI, monitoring, organize teams around services, etc. From my friends in the bay however, I hear the code itself is mostly written and band aided over and over again with refactoring and rewriting seen as “wasting time” when you could be writing more band aids or improving operations. Does the band aid and if it’s not broke don’t fix it and do exactly what you need to fix it approaches really yield the same or better results as approaching software as a craftsmen? How do you convince an AWS engineer that these things are important when what’s in prod is working and a rewrite just seems like pot stirring? Or a refactor isn’t critical work to add more features?