Ask HN: Is speed of delivery the most important metric in productivity?

I'm fairly new to the field and relatively late to the party (because I'm old), but a recurring theme that I'm noticing in my current company (which is a small startup) is how the faster you deliver the better you look to the CEO and even CTO's eyes.

In hour fairly infrequent meetings other engineers have raised the point that we should start valuing code quality and proper testing to our codebase, only to be met with arguments such as "the customer doesn't pay for good code".

Furthermore, most likely an anecdotal bias and nothing else but I want to mention it: Online elitism revolves around shipping speed too. Comments like "I can build X in Y hours", "I can skim the docs and build what I want with Z library in less than a day", and so on.

How does everyone feel about it? Maybe it's just me but it feels weird. It's kinda like everyone I mentioned feels like there are no trade-offs to be concerned in regards to speed over quality or people decided that there's no reason to bother ourselves with contemplating what we're trading off speed with. Also, I feel that because quality is subjective and perfect is the enemy of done, people rely on objective metrics like "time taken".

Is there truth and merit to this observation?