This question already has an answer here:
I had a conversation once with a with a senior development manager. I said that I aimed to produce "good" code, meaning code that is high quality. He said that good code is functional, performant and secure, and "quality" is not even an issue.
His justifications were that what makes good quality code is subjective, and that in their team people tend to specialise in certain areas of the software, so that it is nearly always developer X who maintains class Y. He added that if that developer leaves or changes responsibilities then the new developer might totally rewrite class Y anyway, so there is no point in maintaining quality standards across the team.