cross-posted from: https://lemmy.bestiver.se/post/1210182
Building relationships with customers through support didn’t turn out as hoped
cross-posted from: https://lemmy.bestiver.se/post/1210182
Building relationships with customers through support didn’t turn out as hoped
Completely disagree.
The only two reasons for telemetry are selling your data, or outsourcing QA.
deleted by creator
I believe that’s what they’re saying, that if released software has any bugs that users encounter, and the developers want to know about them to fix them, they’re “outsourcing QA” to the users.
So yeah, good luck creating software and updates with literally no issues :P
QA happens before release. Of course that doesn’t prevent some bugs from slipping through, but instead of waiting for the user to break stuff, I broke it on purpose, working in QA.
I seriously don’t trust any telemetry. Maybe my “paranoia” or whatever makes me heavily biased.
Telemetry tends to be put in reactively after something broke. Barn door, horse bolted, etc. Also, even when it’s done proactively, devs often often aren’t aware of what’s relevant and actionable in a support context.