The Origin Story of Every Bad UI
Description
This is a two-panel meme that humorously links parental choices to future software quality. The top panel features a stock photo of a pregnant woman holding a glass of red wine and a cigarette, with the caption, 'No it doesn't affect my baby'. The bottom panel, labeled '20 years later:', shows a screenshot of a dropdown menu for selecting a month on a web form. The list of months is completely jumbled and not in chronological or alphabetical order (e.g., April, August, December, February). The joke implies that the child grew up to be the developer who implemented this horrifically bad user interface element. For experienced developers, an unsorted list of months is a classic sign of lazy, careless programming and a complete disregard for user experience, making it a perfect punchline for the setup
Comments
27Comment deleted
You call it a bug, I call it O(1) month selection. The user just has to learn the hash function
Twenty years later you can spot the kid: they populate the month dropdown with `SELECT DISTINCT name FROM months ORDER BY name` - apparently prenatal Cabernet disables the part of the brain that knows about ENUMs and integer sorting
This is what happens when you let the intern implement date sorting using a custom comparator function they found on Stack Overflow that was actually for sorting Pokemon by their Pokedex number in a different regional variant
This is what happens when you sort dates as strings instead of proper date objects - 20 years of technical debt compounding into a dropdown that makes users question their own sanity. The 'NA' option nestled between May and November is the chef's kiss of someone who said 'we'll refactor this later' in 2003. It's the software equivalent of that TODO comment from the original developer who's now a CTO at a different company, blissfully unaware their quick fix is still haunting production forms and making UX designers weep into their Figma files
You can tell Month is VARCHAR: lexicographic order, ‘NA’ promoted to the 13th month, and the placeholder persisted - turns out calendars are easier than null semantics
Mom's merlot hardcoded the null month - 20 years later, still failing required field validation
Nothing says enterprise like a required month field whose domain is ['No Selection', 'NA', 'April'…], sorted by the order tickets were filed
how does No Selection get to go at the top??? Comment deleted
Framework added it😄 Comment deleted
maybe default value? Comment deleted
what's wrong with being born in December? Comment deleted
you are the smaller of your classroom... Comment deleted
No, im the oldest one😎 Comment deleted
are you the teacher? 😂 (btw, I wanted to mean that… 🤦♂️) Comment deleted
This shit gave me a headache Comment deleted
Is this better or worse than zero indexing months? Comment deleted
Astrology was created for this form Comment deleted
Aaaa Comment deleted
Its sorted Comment deleted
the joke just leaves the group Comment deleted
Got it Comment deleted
@devs_chat Comment deleted
Spasibo brat Comment deleted
? Comment deleted
Zhmu ruku, drugoi brat Comment deleted
Thank you Comment deleted
The problem is NA and No Selection... Both are same... Comment deleted