• 2 Posts
  • 105 Comments
Joined 3 years ago
cake
Cake day: April 27th, 2023

help-circle





  • People have a psychological bias to humanize anything that communicates with them and companies are trying to latch onto that mechanism because they benefit when people get an emotional attachment to websites. So I think Google and many others are trying to make people think of websites as things with agencies, rather than machines controlled by people. And yea I think they are partly successful.

    Not dissimilar to how LLM AI is marketed nowadays.

    My mom asked me the other day whether a virus warning was a scam or not. It was a webpage in her browser. She did not understand that it was not her computer system warning her, but just the website itself. People can’t even tell the difference between their operating system and their apps.






  • Not sure about that one but the following one:

    In each language, the words for yes and no never change, regardless of which question they are answering.

    This happens in Danish actually. Example:

    Kan du lide is? (Do you like ice cream?)
    Ja
    Kan du ikke lide is? (Do you not like ice cream?)
    Jo

    So in Danish we have “ja” which means “yes” but “jo” is used instead when answering a negative question, so as to confirm what the negative question asked. This is kind of annoying in English cause if you ask “Do you not like ice cream?” then if you say “yes” does that mean “yes I like ice cream” or does it mean “yes I do not like ice cream”? That’s what “jo” disambiguates.






  • While there certainly is some blame on the programmers (to the extent that it is useful to even assign blame), I would say it is hardly fair to blame programmers for most mistakes.

    Bugs are a fact of life - the presence of bugs can hardly be blamed on a specific programmer. Rather, it is a result of the resources assigned to a project and its quality assurance. Yes, at the end of the day it comes down to the lines of code written, but everything and anyone involved in the process up to that point (like designers, project managers, people managers and of course executives at the top) are to blame as well. Especially the decision-makers who deprioritized security or quality assurance are to blame, much more so than the programmer who wrote the line.