Actually, except for the deepest debugging data that only a programmer would want, you’re incorrect. And the conversation wasn’t just about that one minority type of data set.
Focus group and survey can help a lot as to the “why”, or the perception of things. Telemetry helps with the quantitative, the how and the what quite a lot more. Users often can’t even remember the sequence of events, or even how they reached a given situation.
All that information is important for the dev itself sure, but also for the UI people, the UX, the product manager, etc.
All that information is important for the dev itself sure, but also for the UI people, the UX, the product manager, etc.
I mean, I just retired from a career as a self-employed incorporated UI/UX software developer for Fortune 100 companies, but what the fuck do I know, right?
The data telemetry that you are describing is data overload and ends up being not efficient to know. The truth gets lost in the quantity noise.
You have to study the usage patterns of how people use the software, by actually watching people use the app, and you don’t get that from just some counter in memory counting how many times a certain button was pressed, there’s no gestalt in that data set. Great data for selling to third parties, but not for helping you with the UX of an app.
It’s my professional advice that I feel confident in the opinion I expressed on this matter, learned from literal experience on the ground.
It’s my professional opinion, as a current software engineer that what I said is my reality. If your telemetry was useless, it’s because it was poorly done, what can I say?
CosmicCleric@lemmy.world 1 year ago
Actually, except for the deepest debugging data that only a programmer would want, you’re incorrect. And the conversation wasn’t just about that one minority type of data set.
Yawnder@lemmy.zip 1 year ago
Once again, no.
Focus group and survey can help a lot as to the “why”, or the perception of things. Telemetry helps with the quantitative, the how and the what quite a lot more. Users often can’t even remember the sequence of events, or even how they reached a given situation.
All that information is important for the dev itself sure, but also for the UI people, the UX, the product manager, etc.
CosmicCleric@lemmy.world 1 year ago
I mean, I just retired from a career as a self-employed incorporated UI/UX software developer for Fortune 100 companies, but what the fuck do I know, right?
The data telemetry that you are describing is data overload and ends up being not efficient to know. The truth gets lost in the quantity noise.
You have to study the usage patterns of how people use the software, by actually watching people use the app, and you don’t get that from just some counter in memory counting how many times a certain button was pressed, there’s no gestalt in that data set. Great data for selling to third parties, but not for helping you with the UX of an app.
It’s my professional advice that I feel confident in the opinion I expressed on this matter, learned from literal experience on the ground.
Yawnder@lemmy.zip 1 year ago
It’s my professional opinion, as a current software engineer that what I said is my reality. If your telemetry was useless, it’s because it was poorly done, what can I say?