Ask a developer the perfect date and they return DD/MM/YYYY

Level 1: When "Date" Means Two Things

Someone asks, "What's your perfect date?" — meaning a romantic evening, candles, maybe a movie. The reply treats "date" as in calendar date, and answers with the way you write the day, month, and year: day first, then month, then year. It's like asking someone "what's your dream match?" and having them describe the little wooden stick you light fires with. The laugh comes from the swerve — and from knowing that the person answering has genuinely spent more time arguing about how to write dates than going on them.

Level 2: Why Programmers Care About This At All

A date format is just the convention for writing a calendar date as text:

The problem: the first two are indistinguishable for days 1–12. If a user in London types 05/02/2019 into a form built by a developer in Chicago, the system may happily store May 2nd. Early in your career you'll meet this as the bug report "the date is wrong but only sometimes" — and "sometimes" turns out to mean "only for days after the 12th, or only for users in certain countries."

This is why codebases lean on standards (ISO 8601 for text, Unix timestamps for arithmetic) and on battle-tested libraries instead of string slicing. It's also why the reply is instantly recognizable as developer humor: only someone who has been burned by ambiguous dates answers a romance question with a serialization preference. The format isn't the joke; the trauma is.

Level 3: Format Wars Never Change

The screenshot is a clean bait-and-switch: Riyike asks the classic icebreaker — "What is your idea of 'the perfect date'?" — and Femi Lee deadpans:

DD/MM/YYYY Other formats can be confusing really

The pun works because the answer is technically responsive while answering an entirely different question, the signature move of engineer humor. But the second line is where practitioners feel the sting, because "other formats can be confusing" is the understatement of several decades of data corruption. 03/04/2019 is March 4th in Ohio and April 3rd in Oxford, and there is no way to tell from the string itself. This ambiguity is only detectable when the day exceeds 12 — meaning roughly the first twelve days of every month, your bug is statistically invisible. That's the cruelest class of defect: one that passes tests, ships, and then quietly books a customer's flight for the wrong month.

The deeper irony seniors will savor: the punchline confidently declares DD/MM/YYYY perfect, and it isn't. ISO 8601 (YYYY-MM-DD) is the actual engineering answer — big-endian, unambiguous, and lexicographic sort equals chronological sort, which means your log files, S3 keys, and filenames order themselves for free. DD/MM merely swaps one regional convention (most of the world) for another (the US's MM/DD), perpetuating the exact locale-dependent parsing nightmare that haunts every strptime call, every Excel import that silently mangles dates into integers, and every API that returns "02/03/04" with no documentation. The tweet is thus a meme about pedantry that invites a further level of pedantry — fully self-sustaining content, like the date-handling bugs themselves. Somewhere between this, timezones, and the fact that JavaScript's Date constructor parses strings differently across engines, lies the reason "never roll your own date library" became folk law.