> However, blindly adhering to a zero-bug policy can lead to wasted effort on issues that don’t matter to your customers or your product’s success.
This is kind of like insisting on 100% test coverage. Sure, you _can_ hit that mark if you really put in the effort, but there's a point at which the value you're adding isn't worth the opportunity cost.
I ran into a situation at work today that prompted me to write up a lesson I've learned over my past 20+ years of working in the field. In my experience, both software developers and software testers often don't think about this.
> However, blindly adhering to a zero-bug policy can lead to wasted effort on issues that don’t matter to your customers or your product’s success.
This is kind of like insisting on 100% test coverage. Sure, you _can_ hit that mark if you really put in the effort, but there's a point at which the value you're adding isn't worth the opportunity cost.