4 ms·
I would argue that using your own product and talking to your customers is the only way to make good and useful products. Telemetry may have a good use case (al
by eestrada 4y ago
I would argue that using your own product and talking to your customers is the only way to make good and useful products. Telemetry may have a good use case (although I struggle to find one), but it isn't a substitute for dogfooding and direct customer interaction.
- deafpolygon 4y agoThe true use case here is to get you used to the idea of telemetry in your tool chain, then move the goal post further down the road. In a few years, it'll be encouraged to put telemetry in your library ("Why?" "We've already had it in the tool chain this isn't any different!") then eventually, have every application sending telemetry data to Google's servers. If you think this is ridiculous, remember they built Chrome with telemetry embedded .. why? Not for improving services. To build better targeted advertising. Remember Android OS? Yes. But there's still push back and the primary group of people resisting this at large are developers and the more technically inclined.