▲ 116 ▼ Unpopular truth: Telemetry collection actually happens because people are garbage at being helpful to support (www.uncommonapps.nyc) submitted 4 months ago by Fontasia@feddit.nl to c/technology@lemmy.world 58 comments fedilink hide all child comments Building relationships with customers through support didn't turn out as hoped Comments
[+] mabeledo@lemmy.world 4 points 4 months ago (3 children) [deleted] permalink fedilink source parent hideshow 3 child comments replies: [–] kuberoot@discuss.tchncs.de 4 points 4 months ago (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] NecroticEuphoria@lemmy.ml 1 point 4 months ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] phutatorius@lemmy.zip 1 point 4 months ago* (last edited 4 months ago) 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. permalink fedilink source parent
[–] kuberoot@discuss.tchncs.de 4 points 4 months ago (2 children) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] NecroticEuphoria@lemmy.ml 1 point 4 months ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] phutatorius@lemmy.zip 1 point 4 months ago* (last edited 4 months ago) 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. permalink fedilink source parent
[–] NecroticEuphoria@lemmy.ml 1 point 4 months ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] phutatorius@lemmy.zip 1 point 4 months ago* (last edited 4 months ago) 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. permalink fedilink source parent
[–] phutatorius@lemmy.zip 1 point 4 months ago* (last edited 4 months ago) 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. permalink fedilink source parent