• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle









  • I can only speak from the experience of one app at one company, but data we collected was for troubleshooting. Mainly because customers will email us stuff like “your app doesn’t work!!! Worst company ever!!” And absolutely no identifying information whatsoever. To make matters worse they’ll email with an email that they didn’t give us as a customer so how in the world are we supposed to help‽
    So we collect enough data so whoever in the company might need to help them can actually do so.
    There’s a lot of “this app is impossible to use!!!” That we find out with enough data collection is just them refusing to hit the GIANT button in the middle of the damn screen that would solve their problem. I hate users.
    I believe we answered questions in the Apple and Google stores that says that we collect information and send it to 3rd parties (because analytics platforms are technically 3rd party) but not to sell it. I don’t know if that distinction is clear on the stores though.





  • kionay@lemmy.worldtoProgrammer Humor@lemmy.mlwhy not a,b or x,y?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 year ago

    I prefer index variable names that are two words. The second word is always ‘index’ and the first word describes the enumerable objects. carIndex, productIndex, thingIndex

    I’m not paid by the character count. Longer and more descriptive is better. Long lines that go past your 1080p monitor are probably not long because of variable names but because you insist on doing many things in one line (quit doin’ that). For small functions this isn’t necessary, but too often I’m shunted to the middle of a big function with two or three indecies doing acrobatics over one another and while working on it I have to constantly remind myself that this i and j mean particular things.