So you've got this low code quality that somehow doesn't impact product quality but at the same time makes someone's life worse? Can you give me a concrete example? Help me understand. I'm coming at this from having been in test for a long time before product, I care quite a bit about cquality, so it's really fascinating to see you respond this way.
> So you've got this low code quality that somehow doesn't impact product quality ...
Low quality code always impacts product quality in a negative manner. That is why it is "low quality code."
"High quality code" also impacts product quality, but in the predictably positive manner; fewer defects, ability to be enhanced, understandable behavior, etc.
Of course it impacts product quality, in fact that's really what matters, code quality is just a useful proxy for that since they're so highly correlated.
No, you made the point of saying that anything which doesn't affect the business is unimportant. Looking at the quality of software products by the largest and most successful big tech companies, it appears quality is not important. You can see how this is contradictory.
