• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle













  • I replied elsewhere but YES! Telemetry is notorious for causing devs to hyperfocus on shit features due to their high usage. Just because a user is clicking X over Y doesn’t mean Y sucks and X is better. Maybe Y is in their periphery, or camouflaged by the background artwork or worded badly. But hey, since X gets a lot of clicks, it must be good, right?


  • heyoni@lemm.eetoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    edit-2
    1 year ago

    How about shit breaking because everyone at some point is a bad programmer? Even Apple Music doesn’t work when I walk into the elevator until halfway through presumably because hitting play sets of a bunch of useless blocking network calls for music I have saved locally.

    What those calls are, I can’t say for sure. Downloading artwork, license checks or telemetry. I’d venture to guess it’s the latter since music will play with placeholder artwork on a slow connection and license checks aren’t required if the subscription was recently validated (works offline for days).

    But who really knows. I never bothered to inspect the traffic. The point is, if a company like Apple is creating such a crummy experience for a function so absurdly basic, you can imagine how easy and prevalent telemetry based user degradation is. Go browse the web with a tracker blocker and tell me it isn’t snappier.

    PS: I’m also a programmer and collect error reports. So many developers will forego using connection pools, much less collect data with async api’s.

    And let’s not even get into how telemetry is a shit tool that is misused 99.99% of the time and only used to surface popular features that aren’t necessarily good features only because we attach causation to every metric (x feature is highly used, therefore it must be good).