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.
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.
Are you an expert on the subject being discussed?
I am.
Also, there’s just one reality.
If your telemetry was useless, it’s because it was poorly done,
How, exactly, can telemetry be collected poorly?
You totally ignore my points of collecting that much data becomes ineffective and becomes ‘white noise’, as well as how that data would benefit resale more than it would UX analysis.
what can I say?
You could just move on, Internet Warrior.
You’re trying to tell an expert on the subject we’re discussing that they’re wrong about something that they’re telling you they’re very sure of, from many years of experience.
That’s moving the goalpost. We were talking about improving UX for humans, not bug tracking.
what’s used and what isn’t used
You can gather that from non-telemetry means as well. Also, if you’re adding functionality into an application without the analysis and design portion of the development cycle not identifying them as little-used features, then you’re doing software development wrong.
You can call yourself an expert as much as you want, it’s a tool that’s useful to me, so you saying it’s white noises and not useful bears no weight
Well, I can’t stop you from putting your fingers in your ears and going “LA! LA! LA! I CAN’T HEAR YOU!” either, but that doesn’t make you right, or smart.
Me? I listen when an expert in a field tells me something (especially when its for free!), it usually benefits me in the long run.
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.
deleted by creator
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.
deleted by creator
Are you an expert on the subject being discussed?
I am.
Also, there’s just one reality.
How, exactly, can telemetry be collected poorly?
You totally ignore my points of collecting that much data becomes ineffective and becomes ‘white noise’, as well as how that data would benefit resale more than it would UX analysis.
You could just move on, Internet Warrior.
You’re trying to tell an expert on the subject we’re discussing that they’re wrong about something that they’re telling you they’re very sure of, from many years of experience.
deleted by creator
That’s moving the goalpost. We were talking about improving UX for humans, not bug tracking.
You can gather that from non-telemetry means as well. Also, if you’re adding functionality into an application without the analysis and design portion of the development cycle not identifying them as little-used features, then you’re doing software development wrong.
Well, I can’t stop you from putting your fingers in your ears and going “LA! LA! LA! I CAN’T HEAR YOU!” either, but that doesn’t make you right, or smart.
Me? I listen when an expert in a field tells me something (especially when its for free!), it usually benefits me in the long run.
deleted by creator
You’re not being intellectually honest.