35 ms·
Falsehoods Programmers Believe About Names
- DrJokepu 16y agoNo, these are falsehoods people who define the requirements believe about names. That's very often not the same as the programmer, especially at large organizations.
- Deestan 16y agoIf the programmers actually adding the constraint to their systems didn't also believe the falsehoods, they would have written better error messages than, in essence, "You typed your name wrong!".
- derefr 16y agoUser-facing error messages are frequently dictated by the requirements as well.
- olliesaunders 16y agoCan anyone explain some of the more esoteric points on this list? Like "People’s names are all mapped in Unicode code points", for instance.
- dagw 16y agoI'm not sure of all the details, but the Unicode people kind of screwed up when doing Japanese. From what I understand there are several older variations on characters not in common use, but that occasionally show up in names (and old Japanese literature), that can't be encoded in Unicode.
- ars 16y agoIf that's the case, they can't enter it into a computer anyway, so don't worry about it.
- philwelch 16y agoThere's no Unicode code point for the unpronounceable symbol which served as the name of The Artist Formerly Known As Prince, before he again became known as Prince.
- jimbokun 16y agoUndoubtedly due to all the problems he had filling out forms on the Internet.
- alextp 16y agoI think he meant the musician formerly known as Prince for this one.
- LogicHoleFlaw 16y agoWell, once again known as Prince, anyways.
- smallblacksun 16y agoThe artist formerly known as the artist formerly known as Prince.
- jplewicke 16y agoThe former Once and Future Prince?
- Grinnmarr 16y agoI'm not sure if you are being snarky or just ignorant, but the "The Artist..." is the commonly accepted usage and descriptor http://www.citypages.com/1999-06-23/news/the-people-formerly-known-as-fans/ http://www.citypages.com/1999-06-23/news/the-people-formerly...
- bokchoi 16y agoThere is also the guy in the credits from the movie Fargo who uses a Prince symbol on it's side. As far as the Artist Formerly Known As Prince symbol lying on its' side with a happy face in the middle, in the credits: "I'm the storyboard artist formerly known as J. Todd Anderson. That's all I can say about that." It's a private joke between J. Todd and the Coens. Prince and the Coen brothers are both from Minneapolis. (Dayton Daily News: 3/22/96) http://www.imdb.com/name/nm0026824/bio http://www.imdb.com/name/nm0026824/bio
- deleted 16y ago[deleted]
- rbanffy 16y agoI cannot discard the possibility my name was originally expressed in Hungarian rovásírás. AFAIK, it has not been assigned to any Unicode region. I was taught rovásírás as a kid, by my grandpa. I can live with the romanized version. It's been in use for more than a thousand years and it's a bit late to complain.
- GFischer 16y agoSome countries, like mine (Uruguay), have a unique identifier for people - in Uruguay it's called "Cédula de Identidad" which would translate to Identity Card. http://en.wikipedia.org/wiki/Identity_document http://en.wikipedia.org/wiki/Identity_document It even has a nice check digit. But even that breaks in some cases :) so Patio's point applies. Still, it makes building local-only apps easier.
- techsupporter 16y agoSome case #46c: The person is a citizen of a country with a national identity card, yet resides in another country wherein he or she has lost that identity card, cannot return to the country of citizenship to replace said identity card, and country of citizenship will not replace the identity card outside of that country. :) (Hello, fellow Uruguayan)
- danh 16y agoFor a good illustration of the possible weirdness of names, see http://en.wikipedia.org/wiki/Pablo_Picasso http://en.wikipedia.org/wiki/Pablo_Picasso
- RyanMcGreal 16y agoI'm sorry, but your name has too many letters. Please enter a shorter name.
- mseebach 16y agoA contemporary example: http://en.wikipedia.org/wiki/Karl-Theodor_zu_Guttenberg http://en.wikipedia.org/wiki/Karl-Theodor_zu_Guttenberg
- danh 16y agoEven more contemporary is young Brfxxccxxmnpcccclllmmnprxvclmnckssqlbb11116 (pronounced Albin): http://en.wikipedia.org/wiki/Naming_law_in_Sweden http://en.wikipedia.org/wiki/Naming_law_in_Sweden
- spectre 16y agoMost of the items on that list are pretty realistic, but there are a few you can safely ignore. For example image the response you'd get trying to sign up for a bank account (in person), if you told them you didn't have a name.
- patio11 16y agoDefine "safely". If you write code for a hospital that handles this case poorly, when a premature infant is found abandoned in a toilet, you might end up debugging from the ER.
- smallblacksun 16y agoJohn/Jane Doe
- ars 16y agoNo, they call them Baby Boy, and Baby Girl - it even goes on the birth certificate.
- Semiapies 16y agoDefine "poorly". Hospitals I've worked with just tend to put in codes for unnamed babies (such as "NBM", "NBF", surname if known, etc.) for the name fields of legacy programs. If you over-heavily relied on the names in the first case, you'd have a big problem with multiple baby John Smiths in the maternity ward.
- vidarh 16y agoThat's all well and fine if you're building a system for a bank. Not so much if you're working on a project for the UN High Commissioner for Refugees or similar agency. So, yes, there are a few you can safely ignore. The problem is the set you can safely ignore is probably different for almost every job you'll have.
- tudorw 16y agowhat about a number, can't we all just be a number... I'll start things off, call me 1
- stcredzero 16y agoThis is a reference to a short story? Or was it a New Yorker cartoon?
- Sukotto 16y agoOh good, I always wondered who number 1 was
- hugh3 16y agoYou are number six.
- roqetman 16y agoShould the number be a collection of binary digits, decimal...
- RyanMcGreal 16y agoObligatory: http://weblog.raganwald.com/2007/09/you-suck.html http://weblog.raganwald.com/2007/09/you-suck.html
- JulianMorrison 16y agoI'm sorry, but if your name doesn't fit into Unicode, you need a new name. You do not have the right to your own character encoding and font (on someone else's website).
- hopeless 16y agoThere are people who insist on a particular capitalisation of their names (i.e., all lower-case, irrespective of grammar rules) which is surely no different from using characters outside the Unicode set. I'd be very careful telling people what "rights" they have around their names. EDIT: you can't really control what other people call you but you certainly can control what you call yourself.
- JulianMorrison 16y ago"which is surely no different from using characters outside the Unicode set" - not when you are thinking in terms of making a program that will support it. A program will happily render Mr bob smith's name in lower-case if that's how he entered it. But Ms non-Unicode-squiggle is out of luck, and I don't have much sympathy.
- dagw 16y agoYea, how could 80 year old Ms non-Unicode-squiggle's parents have been so cruel and thoughtless that they didn't check the unicode spec before naming their child. Screw them and their lack of foresight and time machines.
- brlewis 16y agoFor the admiration of your peers, identify the subset of this set of assumptions embodied in the "Leave a Reply" form at the bottom of the article.
- patio11 16y agoYeah, I concede, Wordpress has buggy name validation logic for the SQL injection boxes.
- pmjordan 16y agoThis is all very interesting (and even humorous), but I'd appreciate something more constructive. How do we implement a name field on a website in spite of all this weirdness?
- jpr 16y agoHuh, isn't it obvious? Accept anything as a name.
- smackfu 16y agoAnd then when you get a business requirement to sort by last name, tell them "there is no such thing as last names." Then when they finish laughing, hack up some system to split the single name field that doesn't work very well. (It gets even worse when you have unusual sorting rules that really only apply to Western names, like treating Mc and Mac the same.)
- patio11 16y agoTrue story: I once told a customer that their requirement to "sort by last name" was likely impossible to satisfy without reworking the system, given what I knew about their user base. It turned out that I was right: the majority of their staff was Japanese, who expect Japanese lexicographic sort. However, they also had visiting professors from overseas, who largely could not understand Japanese lexicographic sort. (There are actually two common lexicographic sorts in Japanese, based on two ways to order the sounds of Japanese. We use the "table of fifty sounds" method, under which Tanaka comes after Aki but before Sato.) My customers said "Fine, alright, two sort features. One for Japanese, one for foreigners." They were less than happy when I told them that foreigners haven't agreed on lexicographic sort, either. (To use one example I'm familiar with, in Spanish, "ch" is one letter, so Chisako comes after Consuela.) Oh, there is a separate right way to order prefectures. (Which I learned about in an email from a coworker saying "Patrick, come on, use some common sense next time. Have you ever seen prefectures listed lexicographically before?!")
- 16y ago
- wisty 16y ago++ People's last name is their "family name". ++ People's first name is their "family name". ++ People have first names and last names.
- coderdude 16y ago>>People's first name is their "family name". I may be mistaken but I believe this is true in Vietnam (and probably other countries as well).
- josh33 16y agoMongolians use their Father's name as their surname, but they write it first. So if my name would be Brad's Josh. While you may think that they should just write it backwards, that isn't how they write it, and they shouldn't be required to translate their names for our systems necessarily.
- NickPollard 16y agoThe point he is making is that people make one assumption or the other, deepending on the culture in which they live, when actually it varies. In the western world, we assume that someone's family name is their last name. In countries such as Korea, people assume that someone's family name is their first name. Either assumption can be wrong if you're dealing with international customers. Some people might not even have a family name.
- coderdude 16y agoJust so it's clear, I'm not refuting what he said but rather supporting it with a tidbit from my memory, as you have done as well. :)
- wisty 16y agoAlso China, and another reply says Mongolia.
- deleted 16y ago[deleted]
- JoeAltmaier 16y agoMiss Manners says "People's names are spelled and pronounced exactly as they say they are"
- tomjen3 16y agoYeah, but if it can't be expressed as unicode you are not going to be able to use it on my system. And I am not even going to say sorry.
- JoeAltmaier 16y agoWhich is quite consistent with being impolite.
- pyre 16y agoDoes this mean that you view Unicode as perfect and encompassing of all the characters currently in use in the world?
- ars 16y agoMakes no difference. You have to work with what you have. It's not like the programmer can do anything about it.
- pyre 16y agoThere's a difference between working with what you have, and blaming people for using the 'wrong' characters in their name. From the post I was replying to: > And I am not even going to say sorry. With comments like this, one comes off as a douche, which isn't exactly going to engender trust with potential customers/clients. Whether it's 'your' fault or not, how you deal with your potential customers/clients is what really matters.
- JoeAltmaier 16y agoAnd the hated "Its ok to hash names into a 32-bit table, and then tell the user "Stieg Eugene Janakowski is already in use"
- Nekojoe 16y agoA question mark can be part of your name - http://news.bbc.co.uk/1/hi/sci/tech/8206280.stm http://news.bbc.co.uk/1/hi/sci/tech/8206280.stm Certain characters like the defunct yogh have had issues in Unicode - http://en.wikipedia.org/wiki/Yogh http://en.wikipedia.org/wiki/Yogh http://news.bbc.co.uk/1/hi/magazine/4595228.stm http://news.bbc.co.uk/1/hi/magazine/4595228.stm Some names can be changed if they're cruel or too unconventional - http://news.bbc.co.uk/1/hi/7522952.stm http://news.bbc.co.uk/1/hi/7522952.stm http://news.bbc.co.uk/1/hi/magazine/6939112.stm http://news.bbc.co.uk/1/hi/magazine/6939112.stm http://news.bbc.co.uk/1/hi/world/asia-pacific/6937327.stm http://news.bbc.co.uk/1/hi/world/asia-pacific/6937327.stm
- kroger 16y agoFor those confused what an article about zombies (first link) has to do with questions marks in one's name, here's the relevant quote: "Professor Robert Smith? (the question mark is part of his surname and not a typographical mistake)"
- kroger 16y agoAnd, of course, his name looks funny when someone is asking a question: "Is that you Professor Robert Smith??" And I wonder if he introduces himself as "Robert Smith Question Mark" ;-)
- jcl 16y agoCoincidentally, I ran across Scott Shaw!'s homepage today: http://www.shawcartoons.com/bio.php http://www.shawcartoons.com/bio.php (...although there are plenty of other names with exclamation points, due to languages like Xhosa.)
- Vivtek 16y agoThis is almost as bad as the address question. I go by my middle name (my parents thoughtfully gave me my father's first name and even middle initial, which has caused no end of confusion for many a credit bureau over the years). Unfortunately, the State of Indiana's birth certificate system assumes beyond any possibility of override that (1) everybody with children has a first name, (2) that first name has no spaces in it, and (3) the middle name is insignificant. So my kids' birth certificates have my dad's names on them as the father. But hey, who am I, a mere parent, to say what my name is? The real world is full of organic detail that is difficult or perhaps impossible to capture in full in a software system. A name should be just a string. If there are business requirements for sorting or name-of-address (e.g. "Dear Mr. Jones") they should be done with heuristics, with human intervention invoked in sticky situations if necessary. Sure, it's difficult, but you know, a hundred years ago that stuff was all done on an individual case-by-case basis by human beings; if your business assumption is that it can't be done cheaply enough without eliminating human intervention, perhaps you should rethink your assumptions. Otherwise, let me assure you you're irritating every customer whose name doesn't meet your arbitrary rules - in exactly the same way that Google pisses off everybody who needs human support. Everybody thinks that sucks. So at least you should get people's names right, using human intervention if you have to. (And addresses, too, but we just had an extended thread about that, like last month.)
- halostatue 16y agoI am the third person by my full name. My grandfather goes by our shared first given name; my father by our shared middle given name. When the distinction does not matter, I just use my first given name and surname. I never use the middle given name (if someone called me just by my middle given name, I would not respond). If the distinction matters, then whatever system is in place had better be prepared to use my ordinal (III) as significant, but had better not put it as part of my last name. So I will go by: "A-"; "A- Z-"; "A- H- Z-"; or "A- H- Z- III". I never go by "H-"; "H- Z-"; "H- Z- III"; or "A- Z- III".
- Vivtek 16y agoWell, in my case, in addition to giving my my dad's first name, my parents called me by my middle name to distinguish us (a not-unusual practice in families originating in Kentucky/Tennessee; I'm damned lucky they called me Mike instead of Jim-Mike). So for all intents and purposes, my legal middle name is my actual name. It's what I identify with me. That programmers don't get that is a continual source of irritation in my life.
- vidarh 16y agoI have an uncle that has one name on his birth certificate, one on his passport and uses a third - all different spellings of his first name. Particularly confusing to people when his passport has the name spelled one way and signed another. Nobody has been able to get a straight story from him about why.
- wisty 16y agoThen there's William Shakespeare, who spelled his name about 8 (IIRC) different ways. I guess it was a mark of pride for a literary man to be able to write his name however he wanted to, while less educated folk would have to write their names from memory.
- DannoHung 16y agoWow, so recording people's names is an absolutely miserable affair with no likelihood of success. Okay, from now on, all humans will not have names, they will be numbered in ascending order, starting from 1. Boosh. If you want a 'handle' or 'username', you've gotta type it in whatever the encoding system supports. Glad that problem has been solved.
- stralep 16y ago"We want information, information, information." "Who are you?" "The new number two." "Who is number one?" "You are number six." "I am not a number, I am a free man." "HAHAHAHAHAHAHAHA." Btw, why not use encoded pictures?
- colinprince 16y agoAlso, FYI, place names contain all sorts of archaic spellings and characters, for the same reason: they are identifiers, and identifiers cannot and should not be normalized.
- LargeWu 16y agoI think the real lesson here is to to identify those assumptions that may be incorrect for the culture your app is targeted towards and make reasonable accommodations for those cases. The most common ones are probably the easiest to deal with...long names, only one name, punctuation in names. Just relax your validation requirements. We just took care of 99% of names not common to western culture. But I don't think if you are designing an application for, say, the Olathe, KS youth rec sports registration website that you need to be too concerned with folks who have names that have characters not mapped in Unicode. If a person's name is so unusual that it doesn't fit even culturally relaxed input requirements, then they've probably already dealt with that problem before.
- patio11 16y agoI heartily agree that "think what you're assuming" is a good take away here, but can't support "think what culture your app is targeting", because I've seen that virtually invariably blow up straight in the teams' faces. Many Japanese people think racial/cultural homogeneity is practically a national trademark, and this issue has bitten nearly every Big Freaking Enterprise system I've ever seen in Japan. Do you think your global-facing web app or small American town is going to be less culturally diverse than Japan is? That strikes me as highly improbable.
- LargeWu 16y agoI think you're missing my point. Having relaxed standards, such as I outlined, will account for nearly all special cases for a target audience that is reasonably homogeneous. Of course if you are designing a global facing application, then yes, you need to account for a wider range of possibilities. But for many applications designing around cultural norms, but being liberal about what you accept, is perfectly acceptable where the benefit of accommodating for low-probability cases does not justify the costs. And, like I mentioned, in cases for applications targeted towards a homogeneous group, for those that have names so far outside the cultural norms that even liberal standards cannot accommodate them, then they've probably encountered the same thing already before, and they've come up with a way to adapt. Allowing a liberal range is like me going to France and asking for ketchup with all of my food. But having a really unusual name, like one with unmappable characters, is like me going to Riyadh and expecting them to serve booze with my meal. Should I be allowed to drink there just because it's acceptable in my culture? No. It's illegal there, and I just have to adapt whether I like it or not. Again, I emphasize, what I am advocating is for applications with a culturally homogeneous audience, not global, multicultural apps.
- njharman 16y agoFalsehoods users believe about my programs/service. 1) A simple, ascii A-Za-z0-9_ identifier unique to program/service is not required to use my program/service. 1a) My program/service cares deeply about your real world name and all it's nuances and variations. It requires full and complete understanding of your name rather than just a simple authentication mechanism. 2) My program/service will correctly handle the worlds naming conventions past, present, and future to the exclusion of other features / actually shipping some day. 3) Instead of following 80/20 "rule", my program/service will names 100% perfect! 4) My program/service will cater to all languages/cultures/subcultures/niches past, present, and future rather than any sort of target audience.
- IgorPartola 16y agoI like it. I'll take two.
- pyre 16y agoWhat about when your program/service is something where identity matters, like for a credit bureau, a government agency or even a retailer? Just read the complaints here about airliners screwing up people's names by assuming that everything is ASCII/LATIN1/MISC_CHARSET. That makes a difference when you get to the airport and they won't let you on the plane because your ticket and your id don't match. It's also an easily solvable problem. Just include a 'name' field. Make sure that it's sanitized correctly and supports UTF-8 (make sure that your database is properly set up to use UTF-8 as well, or else all manner of problems can happen, least of all queries will get bogged down as the database does charset conversions for string comparisons). If you care so little about the user's name, then why bother to have separate firstname/lastname fields? {edit} With respect to the 'other complaints,' I was referring to the comments on this story: http://news.ycombinator.com/item?id=1438355 http://news.ycombinator.com/item?id=1438355 (The story which is what Patrick's post was in response to).
- MichaelSalib 16y agoJust read the complaints here about airliners screwing up people's names by assuming that everything is ASCII/LATIN1/MISC_CHARSET. Having worked in the airline industry, I can tell you, this is not a case of airlines making a poor assumption. Airline systems are generally incapable of dealing with ASCII, let alone Unicode text. They typically use EBCDIC. That's why you never see lower case characters in your name on a boarding pass. That makes a difference when you get to the airport and they won't let you on the plane because your ticket and your id don't match. Does this actually happen? Because given the fact that airlines have been incapable of printing names that don't can't be described by EBCDIC since, well, forever, I'd assume that they're willing to ignore cases where the name on your ID contains characters that their computer system literally cannot represent.
- edw519 16y agoOh Patrick, as usual you got me to thinking. Then it hit me: the "Name" issue isn't that much different from the "SKU" issue. (SKU is short for Stock Keeping Unit, aka Part Number or Product Number). I have had to deal with this everywhere that has SKUs. No one does it well, but by slowing down and thinking about it, there's almost always a decent solution. There are 2 ways to assign SKUs, sequentially (start with "1" and increment 1 for every new SKU) or not sequentially. I have never seen anyone do it sequentially. (Although some excellent systems keep 2 SKUs, one of which is sequential and is used as the primary key and for all indexing. This is the best way I've ever seen to handle SKUs that change, but that's another story.) Almost everyone wants a smart or semi-smart SKU. So that by simply looking at the SKU, anyone can tell what it is without reading the description. You know, the first digit is Commodity Code, 1 for shoes, 2 for pants, etc. Then another digit for color, another for size, etc. This works well until you have ten colors; then you need 2 digits or alphas. But wait, there's more. Let's put hyphens (or some other delimitter) between the product descriptors and the vendor data, manufacturer data, and customer data. So now you've covered any possible product with your super slick smart SKU naming system. Until something comes along that isn't covered. (Now we have military items with 14 other considerations.) So we come up we a second totally different scheme. Then a third. Then a 4th, etc. So now you can tell anything about an item if you know which scheme it falls under. But wait, there's more. You should be able to enter any SKU into a form field regardless of Smart SKU scheme. (If the first digit is "9", then use Smart Scheme 3. If there's a hyphen in position 3, then use Smart Scheme 8, etc.) Your form logic should be able to intelligently guide the user based on the rules of the template or scheme. I have built apps where users can design and build their own Smart SKU templates, which are then used to enforce compliance and guide operators. These have generally worked pretty well. Is there some way to do the same thing for human names? I dunno, but now you got me to thinking about it. A combination of standard templates and custom templates oughta cover most possibilities. Some basic logic with optional pop-up forms which uses the templates as parameters should work. Something to think about...
- rikthevik 16y agoThis sounds exactly how instruction sets evolve. 32 opcodes? That's plenty! We'll never run out. :)
- GavinB 16y agoMy first name is spelled with a $10 bill. It's pronounced "Gavin." My last name is a picture of a flower. If you represent it at less than 1000x1000 pixels or with washed out colors, you are insulting my heritage. My middle name is a musk ox. How far does politeness dictate that you have to go to accommodate me?
- santry 16y agohttp://vodpod.com/watch/1616920-funny-hugh-laurie-stephen-fry-comedy-sketch-your-name-sir-bbc-comedy http://vodpod.com/watch/1616920-funny-hugh-laurie-stephen-fr...
- pyre 16y agoI think that the bar should at least be set higher than: "Your name does not fit into a Western firstname/lastname format with only ASCII characters, please choose another name." This is on par with expecting everyone to speak English just because you speak English. By the very setup of the form, you are implying that your way is the 'one true way' or at least that you don't care about people that don't fit into your pre-defined set of expectations (i.e. "Don't have a firstname/lastname? I don't care about your business! Your money is no good here!"). How hard is it to just have a 'Name' field that supports UTF8? Sure it's not a 100% solution, but it's a lot better than the 20% (or less) solutions that we have out there right now.
- fforw 16y agoThe puritans had "religious slogan names" like Nicholas If-Jesus-Christ-Had-Not-Died-For-Thee-Thou-Hadst-Been-Damned Barbon ( http://en.wikipedia.org/wiki/Nicholas_Barbon http://en.wikipedia.org/wiki/Nicholas_Barbon )
- mmacaulay 16y agoOnly somewhat related, but first thing that came to mind: http://xkcd.com/327/ http://xkcd.com/327/
- deleted 16y ago[deleted]
- joe_the_user 16y agoCalling a statement a "falsehood" implies there's some truth that can and should replace it. The statements he lists aren't "falsehoods" or "truths", they are approximations - operating assumptions. If your operating assumptions are true enough for a given purpose, there's no reason to change them. If they deviate enough from to generate problems, they will need to be replaced ... with other approximations (not with "the truth"). -- This is why apparently simple and "finished" programs alway need "maintenance" - even the most seemingly simple assumption need tweaking as the world's conditions change.
- jheriko 16y agoThis problem isn't handling names, its validating them and trying to do clever things with them, which is rarely, truly, necessary - especially if its a customer's name that they see on mail, bills etc and that they have the ability to correct... they will validate it for you. I think the real bad assumption is that validation is necessary or even desirable - applying the technique brainlessly to names is the root cause of this problem - you don't really need to make any assumptions.
- yellowbkpk 16y agoIncidentally my friend RJ just experienced a related problem on Facebook. After he got married his name (which includes a hyphenated family name) has 4 capital letters on it. Facebook complains that his name has too many capital letters and will not let him use it. He tried all-lowercase but Facebook automatically capitalizes each word making it look even worse.
- vsync 16y agoIt gets annoying for handles too. I usually just use "vsync" but certain systems smash the first character upcase and it looks ugly as "Vsync". So I try "VSync" and it smashes all characters but the first downcase. Not to mention systems that require usernames to have 6 characters or more, sigh...
- KevBurnsJr 16y agoLets just tattoo a bar code to everyone's forehead and be done.
- Goladus 16y agoIt doesn't matter what programmers believe, it matters what programmers can do with the computers available.
- nradov 16y agoThe HL7 V3 standard has a fairly good data model for dealing with names. http://www.hl7.org/v3ballot/html/infrastructure/datatypes_r2/datatypes_r2.htm#dt-EN http://www.hl7.org/v3ballot/html/infrastructure/datatypes_r2... Combine that with Unicode and you can solve the majority of problems.