Hacker News Reader

Most 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.

View on HN

Define "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.

Define "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.

John/Jane Doe

No, they call them Baby Boy, and Baby Girl - it even goes on the birth certificate.

That'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.

Reply on news.ycombinator.com