21–30 of 527 posts
Could you just have a single field for name and allow anything in that field? The only downside is you can't do something like "Hi ${FIRST_NAME}" in your emails, but the upside is that it basically handles any name or name order, e.g. Indonesian single names, Spanish names with the mother's surname included, etc.
[deleted]
Definitely read https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... if you haven't yet. Then think about what are the requirements your system needs when it comes to names. Does the app need to know what a user's name is at all or is a username enough? Does it need to distinguish the family part of their name for anything? A thing I think is the most general is to just have a Full Name field (min length 1…
More people designing applications need to read it.
Seems more of a stackoverflow question? But: https://github.com/kamranahmedse/design-patterns-for-humans#... https://www.postgresql.org/docs/current/datatype-enum.html I'd have multiple classes handling each one a use-case, and a enum on user's record in order to specify which class to use for each, so that you can compute it from the nationality, but you could also potentially give each user the chance to set it for…
Is it really worth using enum in postgres over a plain string, and optionally a check constraint if you're super concerned about strictness?
Definitely read https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... if you haven't yet. Then think about what are the requirements your system needs when it comes to names. Does the app need to know what a user's name is at all or is a username enough? Does it need to distinguish the family part of their name for anything? A thing I think is the most general is to just have a Full Name field (min length 1…
Thank you for reminding me of this article! More people designing applications need to read it.
https://studyinthestates.dhs.gov/sevis-help-hub/sevis-basics...
Personal opinion. As an Asian person, don’t overthink this. Just have fields for family name and given name to distinguish between the two. Sure, when there’s a text field saying hello “first name last name” it might be flipped but this shouldn’t be a deal breaker or offensive in any capacity. Worst case is you can have a toggle they can click but from a developer standpoint, that might be over engineering for someth…
Use a single text field for the full name.
I would not do this. For reasons of respect, you may need to address a person by either their first or last name (with a title). Addressing a person by their full name can come across as rude (I personally find it rude too, e.g. "Hey John R. Brown, this is your order"), so it's useful to split up "given name" and "family name" into 2 fields so that you don't have to depend on name ordering which varies by culture. If…
Just add a field for the desired form of address, or a nickname.
> Addressing a person by their full name can come across as rude
Stuffy, Maybe, but rude? Calling people by their first name is rude. Calling people by forms of address which don’t exist is rude.
Though it it also may be just "given - family", as well as any other variation informally. So you wouldn't make a mistake with UI
One interesting approach would be to use a regex to detect if the name is written in Hanzi, Kanji or the Korean or Vietnamese alphabets and write the name in whatever format is appropriate for the locality. The Asian people I know would be be unsurprised to see their name rendered western style when written using whatever romanization format their native language uses.
Have you looked at how the tech giants before you have solved this issue?