I think much of this depends what you are employed to do. Sometimes it's about making things less complex, which means good practices, code quality, clean code

I think much of this depends what you are employed to do. Sometimes it's about making things less complex, which means good practices, code quality, clean code and testing means you can afford a bit more risk. Equally, sometimes you employed to just get things done, make it work, even fake it till you make it, proof of concepts, minimum viable products, etc. I've done both, I enjoy both, but they are two different modes of working. Ultimately the answer is "it depends" and milage may vary. Quality is a journey not a destination. Yes, put delivering value above anything else, sometimes that value is quality.