21–30 of 128 posts
Very true, we all know there are 92 genders
You are right. I don't understand why developers should take into consideration any possible psychological quirk of any potential user.
I mean, now that I know I’m wrong, how do I become right?
Very true, we all know there are 92 genders
You are right. I don't understand why developers should take into consideration any possible psychological quirk of any potential user.
You might ask if it should use Mr./Ms. (or Dr. or some other academic title) etc but even that is a bit anachronistic. Maybe this makes sense if you're sending mail to your customer, but even then.
How to solve 50% of your GDPR troubles: stop asking for data you have absolutely no use for (and no, selling customer data is not a legitimate use)
After reading the Falsehoods Programmers Believe About Names, I wonder, what would you recommend as a universal way to store users's names? There seems to be two main options: Store the name in a single field, be correct but lose the option to sort the names reliably. Store the name in two fields, have the users bend over our western form standards but be able to search and sort easily. Do you have any real life expe…
You can't search and sort easily if the names are stored in Japanese. You need 4 fields for that.
Edit: now that I think about it I could think of a disgustingly hacky way to squash them into 2 fields and retain those properties, and by extension into a single field and retain those properties.
I really enjoy these, but where can I find an explanation of what each falsehood means (in particular: the network one)? I mean, now that I know I’m wrong, how do I become right?
After reading the Falsehoods Programmers Believe About Names, I wonder, what would you recommend as a universal way to store users's names? There seems to be two main options: Store the name in a single field, be correct but lose the option to sort the names reliably. Store the name in two fields, have the users bend over our western form standards but be able to search and sort easily. Do you have any real life expe…
> what would you recommend as a universal way to store users's names? It's unsolvable problem. Names are locale and context dependent and there is no way to translate any given name from it's canonical form (which is nonexistent) to any context you would need (except identity function obv). So you store in-context representation(s) of name and don't transform ever. In practice that means you have one or two fields wi…
Earlier quoted context omitted.
> what would you recommend as a universal way to store users's names? It's unsolvable problem. Names are locale and context dependent and there is no way to translate any given name from it's canonical form (which is nonexistent) to any context you would need (except identity function obv). So you store in-context representation(s) of name and don't transform ever. In practice that means you have one or two fields wi…
Let's just rename everyone a GUID and be done with it.
This doesn't seem curated. It just seems like a list (a long one bloated one at that).
After reading the Falsehoods Programmers Believe About Names, I wonder, what would you recommend as a universal way to store users's names? There seems to be two main options: Store the name in a single field, be correct but lose the option to sort the names reliably. Store the name in two fields, have the users bend over our western form standards but be able to search and sort easily. Do you have any real life expe…
I shit you not, there were fields added there that our Western thinking would never dream they are needed, for example plenty of old people from Papua New Guinea added "Grandfather initial" to their name. Or others added "tribe name" as a meaning to somehow show that they are part of an extended family.