Live data from Hacker News

We have an employee whose last name is Null. He kills our employee lookup (2012)

stackoverflow.com

41–50 of 245 posts

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#41
post #6

Reminds me of a story a police reservist told me. Guy got a license plate caled "none," and instantly had thousands of outstanding warrants. (The cop thought "none" was trying a fast one, and so deserved it.)

License plate was X and it had to do with parking tickets.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#42
post #4

As long as we're playing the "Falsehoods Programmers Believe About Names" game again, here's the relevant patio11 article: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b... If you try to validate names, or if you don't safely escape names along with your other user-input strings, you're gonna have a bad time.

My name fail to register surprisingly often, even here in Brazil.

It is Hélder Maurício Gomes Ferreira Filho

Common reasons for failure is being too long and having non ASCII characters, but sometimes it fails for other reasons, for example do not allow me to register without a middle name ( I don't haven't one actually... ), me confused and not knowing how to register Filho ( it is not a family name, neither a surname or a last name, but it is still part of my name. It means Son, my father has the same name as me, without the Filho part), or breaking when it cross check with somewhere ( for several reasons I ended registering my name in several different ways, usually omitting Hélder, that I did not even knew was on my name until I got to school and got forced to use because of stupid rules that assume your first name is your typical name )

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#44
SOAP: the gift that keeps on giving. I built two SOAP APIs for Google (Search and AdWords) and spent way, way too much time on this kind of data interop nonsense. I wrote up a quick summary of why SOAP sucks, it's still my most popular blog post. http://www.somebits.com/weblog/tech/bad/whySoapSucks.html

XML is a terrible encoding for data. Fortunately JSON does pretty well and has mostly replaced it for new stuff.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#45

Earlier quoted context omitted.

Weird, because makes a distinction between int and string.

Python makes a distinction between types, but it has a concept of falsyness (as do many languages, though it is often more restricted e.g. in Ruby only false and nil are falsy IIRC). Falsyness is used in boolean-ish contexts (if, while and explicit boolean conversion), by default all of None (null), False, 0, 0.0, "" (the empty string, unicode or binary) and empty collections ([], (), {}, set()) are falsy and althoug…

GForth uses 0 for 'false' but -1 for 'true'... that confuses me a lot.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#46
post #6

Reminds me of a story a police reservist told me. Guy got a license plate caled "none," and instantly had thousands of outstanding warrants. (The cop thought "none" was trying a fast one, and so deserved it.)

What do you know, there's an xkcd for that too: http://xkcd.com/1105/

There's a relevant XKCD for every situation.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#48
post #45

Earlier quoted context omitted.

Python makes a distinction between types, but it has a concept of falsyness (as do many languages, though it is often more restricted e.g. in Ruby only false and nil are falsy IIRC). Falsyness is used in boolean-ish contexts (if, while and explicit boolean conversion), by default all of None (null), False, 0, 0.0, "" (the empty string, unicode or binary) and empty collections ([], (), {}, set()) are falsy and althoug…

GForth uses 0 for 'false' but -1 for 'true'... that confuses me a lot.

I suppose it's because then it can just compare the first bit.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#49
post #32

Earlier quoted context omitted.

Welcome to the world of (a) standards (b) poorly implemented standards (c) poorly implemented programmers :-)

I blame c. Those mothers should learn how to implement their programmers.

Funny, I read this as "I blame C [the language]". I was taken aback because obviously "null" in C is a 5 byte character array and would never be confused for NULL.

Re: We have an employee whose last name is Null. He kills our employee lookup (2012)

#50
post #3

I had an aunt named Nan, I wonder what her disbursement checks were like :-)

My credit card was charged for $NaN once, due to a bug in a PitneyBowes postage kiosk. I was afraid I'd need to write them a check for 0/0 :-)

I have a photo of the receipt at http://www.righto.com/2008/05/importance-of-software-testing...

Post reply on HN