3 ms·
But when it is used they'll have telemetry on errors that occur during the restore process. So hopefully the next person doesn't have to deal with the same issu
by fbrchps 5y ago
But when it is used they'll have telemetry on errors that occur during the restore process. So hopefully the next person doesn't have to deal with the same issues that the first did.
- chongli 5y agoI believe the GP's point was that if you follow the "remove anything that users rarely use in telemetry data" philosophy then you end up removing the restore feature of the backup software, defeating the entire purpose of backup software in the first place. In other words, just because a feature is used rarely doesn't mean it isn't important to keep around. So much of what's wrong with software these days can be attributed to this "A/B test everything, the data never lies" approach to design.
- yjftsjthsd-h 5y agoPrecisely; frequency of use is not the same as importance, and confluating them is dangerous when you use it to justify cutting features.
- pronik 5y agoJust like Android telling me "you haven't used these apps in a while, let's remove them" while the apps are of the use-once-a-year or emergency kind of software.
- AlexandrB 5y ago> So much of what's wrong with software these days can be attributed to this "A/B test everything, the data never lies" approach to design. Design by focus group where the focus group is the users who left telemetry on/unblocked.
- yjftsjthsd-h 5y agoWe were talking about use stats, not crash reporting (which, yes, is more defensible).