Live data from Hacker News

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

stackoverflow.com

1–10 of 245 posts

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

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

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

#9
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/

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

#10
post #5
post #2

Numerous bugs on github were attributed to the guy with user name 0. He evaluates to false in many PHP applications, too.

Ditto for Python (int 0 at least).

Weird, because makes a distinction between int and string.
Post reply on HN