Hmm, I just got around to reading this tab after opening it several hours ago and can't help but feel like this guy is overthinking this way too much. If a pers

Hmm, I just got around to reading this tab after opening it several hours ago and can't help but feel like this guy is overthinking this way too much. If a person wants to have a first/last name structure in their app/db, fine, let him. Make one of the names optional in the database and only fill it when the submitted data looks like a first/last name structure. Add properties to your model to return whatever you need to display. Some of the things in his list sound like particularly interesting stories, like why he's talking about when a person's name is assigned at birth or 5 years later (what piece of code needs to reference that? why would an app ever need to know that unless it's checking if a person has ever changed their name? Any programmer who can tie his own shoes will know names aren't unique. Ever. Most of the rest of them just make me wonder "why would that ever be an issue???". And oddly, several of them make me think of "hmm, that reminds me of that bug X..." scenarios, none of which were problems with naming, just general programming bug scenarios like forgetting a database comparison on your DB of choice isn't case-sensitive, things like that.