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

help-circle









  • The findings here seem like a real stretch.

    Saying that people can “Accurately” identify names for adults but not children feels tenuous when they only answered correctly less than 25% of the time for children and slightly more than 25% for adults, among four options. That’s barely better than random chance.

    If there really even is any correlation between name and appearance, then as other people have said, this is likely due to factors of age, and popularity of different names at different times. The child group used children only from a narrow range of 9-12 whereas the adult group was broader, so it would be easier to see the influence of age in the adult group.

    I assumed those conducting the study would be very familiar with that bias and try to eliminate it by only using names that were equally popular at the same time as the person’s actual age for each question, but I couldn’t find that information.

    If we assume they DID try to eliminate generational popularity as a factor, there are still more plausible explanations IMO.

    For example, different names are going to be popular among different socioeconomic backgrounds - wealth, education, political leaning, geographic location of the parents will all affect name choice!

    So if there is any correlation at all, my personal conclusion would not be that the name determines who people grow up to be, but that someone’s physical appearance is influenced by their socioeconomic background, and that name also correlates with that background.

    So name is simply a predictor for what background someone grew up with, nothing more!







  • tiramichu@lemm.eetoProgrammer Humor@lemmy.mlSite: "I don't feel so good...."
    link
    fedilink
    arrow-up
    221
    arrow-down
    3
    ·
    edit-2
    2 months ago

    The fade should be slow and subtle. At first the client thinks they are just imagining it, but then they start getting customer support calls about the site being faded, and their bosses are pointing it out too in meetings, and as it happens more and more the panic really begins to set in.

    Finally they reach out to you in a desperation when there’s barely anything left of the site and ask you to urgently fix the problem, and you just shrug your shoulders sympathetically and explain it’s happening because they haven’t paid - but not like in a way that suggests you are doing it on purpose, but a way where it’s simply an unavoidable natural consequence, like if you didn’t pay your electricity bill your power would get cut and the site is slowly “dying” and fading away because of that.

    They’d pay so fast.





  • Technical requirements are often ambiguous when written as free text, the way someone would speak them, because as you have discovered the free text fails to capture where the linguistic stress would be that disambiguates in speech.

    Instead, I suggest using a format that is more suited to text.

    I would recommend a table. Email the customer back with your current interpretation of the requirements, with a column for outcome and a column for value. Ask them to check and sign off on the table, or to correct the table where it is wrong.

    Example:

    Outcome Value
    NULL x
    Complete x
    Cancelled x
    (Other) x

    There are edge-cases with if outcome can be "Complete or Cncelled