Data validation Memes

Posts tagged with Data validation

How Would You Like To Pay Your Na N Pounds?
Javascript Programming Debugging Frontend Webdev
3 months ago 2.7M views 0 shares
How Would You Like To Pay Your Na N Pounds?
When your grocery store's price tag system decides to have a full existential crisis and starts speaking in JavaScript data types. That price tag is literally displaying "£NaN" which is what happens when some poor soul's code tries to do math with something that absolutely, categorically, REFUSES to be a number. Someone's database query probably returned undefined, null, or maybe just the screams of a thousand developers who forgot to validate their inputs. The system looked at whatever value it got, tried to calculate the price, and just gave up on life entirely. "Not a Number? Cool cool cool, I'll just print that directly on the shelf for customers to see. What could go wrong?" Meanwhile shoppers are standing there wondering if they need to pay in existential dread or JavaScript errors. The real kicker? It still shows £3.69 right next to it, so the system KNEW the price but chose chaos anyway.

Set Date Of Birth Validation To 150 Years Old What Could Go Wrong
Backend Programming Webdev Frontend Testing
3 months ago 29.0M views 0 shares
Set Date Of Birth Validation To 150 Years Old What Could Go Wrong
So you thought setting your date of birth validator to accept anyone under 150 years old was being GENEROUS and INCLUSIVE? Congratulations, you've just granted Pharaoh Ramesses II a valid passport in 1976. The man died in 1303 BC and somehow your validation logic was like "yeah, seems legit, he's only 3,279 years old, well within our acceptable range!" This is what happens when developers write validation rules at 2 PM on a Friday thinking "nobody will EVER need to enter a date that old." Meanwhile, Egypt's out here issuing official government documents to mummies for restoration trips to France, and your form is just nodding along like "welcome aboard, your majesty." The real kicker? Someone at the Egyptian passport office in 1974 had to manually enter "-/+/1303 BC" into whatever system they were using, and it WORKED. Edge cases aren't just theoretical anymore when you're dealing with royalty that's been dead for three millennia. Maybe next time set that validation to "must be alive" instead of just "reasonably old."

Cries In SQL Date Time
Databases Backend Programming Debugging
7 months ago 531.5K views 1 shares
Cries In SQL Date Time
Nothing says "I'm a keeper" quite like someone who exclusively uses DD/MM/YYYY and refuses to acknowledge the existence of ISO 8601. While the rest of us are drowning in timezone conversions, locale-specific parsing errors, and that one database that stores dates as strings (yes, really), this guy found his soulmate who thinks there's only one true date format. Meanwhile, your production server is somewhere screaming because someone in the US entered 03/04/2024 and now nobody knows if it's March 4th or April 3rd. But sure, let's pretend other formats are just "a bit confusing" and not the reason we have 47 different datetime libraries in every programming language. Fun fact: There are at least 20+ common date formats used globally, and they all hate each other. The only thing developers can agree on is that whoever decided to make JavaScript's Date() start months at 0 deserves a special place in debugging hell.

The Date Format Holy War
Programming Backend Frontend Webdev Databases
1 year ago 439.2K views 2 shares
The Date Format Holy War
The eternal date format war rages on! While most of the world sensibly uses the pyramid of DD/MM/YY (small to big), and some Asian countries flip it upside-down (YY/MM/DD), the USA just... does whatever the hell it wants with MM/DD/YY. It's like they designed their date format the same way they designed their healthcare system – maximum confusion for everyone involved. The beautiful irony is that only the YY/MM/DD format is actually ISO-8601 compliant and makes perfect sense for sorting. Meanwhile, programmers everywhere silently weep when handling date inputs from international users. Nothing says "fun weekend project" like writing regex to figure out if 03/04/05 means March 4th, 2005 or April 3rd, 2005 or... wait... 1905?