Software teams have to move away from the idea that bugs are a useful way to measure quality.
Software does not have enough self awareness to be afraid of bugs. That's why it works as well as it does.
Testing shows the presence, not the absence of bugs.
Bugs are like over-parented kids. They get a lot of attention. They might be born in the relative quiet of a developer's IDE, but the moment they are exposed to the rest of the world, they live their lives amidst a great deal of fanfare.
Maybe there’s no such thing as a bug. Maybe there are just things that work well and things that don’t work well.
Unfortunately, in the celebration of testing artifacts (such as counting the number of bugs) we forget about the software. All testing artifacts have value to the extent that they impact the source code and therefore the product.
Comprehensive statistics of past bugs are no more useful for software quality than financial accounts of a chophouse are useful for a steak sandwich.