3 ms·
It's not privacy vs stability, that's a favourite red herring around here. The problem is your development process is not capable of producing stable enough so
by blub 9y ago
It's not privacy vs stability, that's a favourite red herring around here.
The problem is your development process is not capable of producing stable enough software. I don't know why that's the case, but you should work on that first.
Deming: "Inspection does not improve the quality, nor guarantee quality. Inspection is too late. The quality, good or bad, is already in the product. As Harold F. Dodge said, “You can not inspect quality into a product"". This goes even more for crash-reporting quality into a product.
- kitsunesoba 9y agoI see what you’re getting at, but the reality is that there’s only so far massaging and rethinking your process can take you. No matter what you do, some number of bugs are going to find their way through. There’s going to be unforeseen combinations of variables and edge cases you’d never predict. The best one can ever do is reduce the frequency of occurrence to a minimum. Bugs are an inevitability, and I’d rather not be at the mercy of my users when it comes to finding out about them.