Approximation is an important tool for compressing information into useable forms. All labels are limited approximations too. Such compression is inevitably lossy, but that is a sacrifice for the sake of practicality. The important question is what level of compression is acceptable for a given context. If I describe the location of a chess piece on the board, I don’t need to specify how far off-center on its square a given piece is, so a 0-7 offset along each of the two axes is enough for game purposes.
When it comes to gender, I think we all agree that [0, 1] is insufficient, but how do we determine what is sufficient? Do we argue that a 2-bit vector (masc, fem) is enough to describe {neither, fem, masc, both} for rough rounding, or do we need more detailed values along those axes, or perhaps a third axis too (or more)?
Honestly, “I found this useful/interesting/amusing/worth leaving a positive comment avout” is the only award I need. Thanks for the words of appreciation ❤️
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Approximation is an important tool for compressing information into useable forms. All labels are limited approximations too. Such compression is inevitably lossy, but that is a sacrifice for the sake of practicality. The important question is what level of compression is acceptable for a given context. If I describe the location of a chess piece on the board, I don’t need to specify how far off-center on its square a given piece is, so a 0-7 offset along each of the two axes is enough for game purposes.
When it comes to gender, I think we all agree that [0, 1] is insufficient, but how do we determine what is sufficient? Do we argue that a 2-bit vector (masc, fem) is enough to describe {neither, fem, masc, both} for rough rounding, or do we need more detailed values along those axes, or perhaps a third axis too (or more)?
This is a very nice and effective blurb, I’m saving this comment for future use
There’s no awards/medals here but take this: 🥇
Honestly, “I found this useful/interesting/amusing/worth leaving a positive comment avout” is the only award I need. Thanks for the words of appreciation ❤️
Maybe a byte using bitflags?