The single most common category of entries for this column is failed handling of NaN, null and undefined. Almost exclusively from javascript in web pages, sometimes in node servers, and almost never any other languages or frameworks. They're getting a bit repetitive but it's our solemn duty to call out failure where we find it. So if you send us one of these, make sure it identifies the source!
"If you want something you've never had, do something you've never done" exhorted Ben.
"Dashed Hope for Jennifer Null," titled an entry from some guy[sic]. "As recently linked from TDWTF article "Not for Nullthing", not only names can break computer systems, but also article content." Stretching, but we'll allow it.
"Where does Batman go on holiday?" asked Morgan. "Nananananana... Nowhere!"
"UBER is ready for driverless vehicles..." Bruce C. "Uber is getting so big, they can't even keep track of their driver's names."
"Well at least the reason wasn't null or NaN," wrote Steve W. regarding CenturyLink. "I've been trying for weeks to use their web page to change my (incorrect billing address). Such progress."
Additional entries on the topic from
Dan
: "we're fresh out of null"
Henrik
: "What is this null music streaming service"
Mike
: "Name: undefined"
Laks
: "In this app, every new user defaults to a nullptr."
and
Jim
: "Think I'll buy $NaCar with this refund!"
and many others were all appreciated and noted.




