Write today's date. If you're American, you probably wrote something like 03/31/2026. If you're from most of the rest of the world, you wrote 31/03/2026. And if you work in data, you wrote 2026-03-31. All three represent the same day. Only one of them sorts correctly on a computer.
This sounds trivial. It isn't. The way you write a date says something about what you think dates are for, and the answer to that question matters more than most people realize.
Three Formats, Three Philosophies
There are really only three contenders. Month-day-year (MDY), used primarily by the United States and a handful of other countries. Day-month-year (DMY), used by most of the world. And year-month-day (YMD), the International Organization for Standardization (ISO) 8601 standard, used natively in China, Japan, South Korea, Hungary, and a growing number of technical contexts everywhere else.
Each one has a logic to it. DMY goes small to big: the day is the smallest unit, then the month, then the year. It's ascending order, and it matches how many languages actually say dates out loud. "The 31st of March, 2026." Clean, orderly, intuitive if you think about dates as building blocks stacking from specific to general.
MDY matches how Americans speak. "March 31st, 2026." You say the month first, so you write the month first. It's not illogical. It's just spoken-word order transcribed to numbers. The problem is that once you strip out the words and leave only digits, 03/31/2026 follows neither ascending nor descending order of magnitude. Computer scientists call this "middle endian," and the name alone tells you how unnatural it is. It's like writing time as minutes:seconds:hours.
YMD goes big to small. Year first, then month, then day. It's descending order, the same way we already write time. We don't write 35:07:14 for 2:35pm and seven seconds. We write 14:35:07. Hours, minutes, seconds. Large to small. YMD does the same thing with dates.
The Sorting Argument
Here's the reason I actually care. If you name a file "2026-03-31_report.pdf" and another file "2026-04-15_report.pdf," they sort chronologically by default. Alphabetical order and chronological order are the same thing. No special software needed. No date-parsing logic. Just filenames in a folder, sorted correctly, forever.
Try that with "03-31-2026_report.pdf." Now your March 2027 file sits right next to your March 2026 file, with everything from April through February jammed in between. And with day-first? Even worse. You get the 1st of every month grouped together, then the 2nd of every month, and so on. It's chaos.
This isn't a niche concern. Harvard's biomedical data management guidelines recommend YYYY-MM-DD for exactly this reason. The United States military uses it for operations. Two separate federal standards, one traceable back to 1968, mandate year-month-day format. Every major database engine treats ISO 8601 as the default. It's already the standard in the places where getting dates wrong has actual consequences.
The Ambiguity Problem
Here's what really gets me, though. Write "01/02/03" on a piece of paper and hand it to someone. Is that January 2nd, 2003? February 1st, 2003? February 3rd, 2001? You genuinely can't tell without knowing what country the person is from. Any date where the day is 12 or lower is completely ambiguous between MDY and DMY.
This causes real problems. The United States Food and Drug Administration and the European Union both now push ISO 8601 for medical device labeling, specifically because date ambiguity was causing issues with time-sensitive patient data. When a label says "Expires 03/04/2026," a hospital in London reads April 3rd and a hospital in New York reads March 4th. That's a month-long gap created by a formatting choice.
YMD doesn't have this problem. Nobody on earth uses year-day-month. So if you see a four-digit number at the front, you know exactly what's coming: year, then month, then day. There's only one way to read it.
So Why Don't More People Use It?
Habit, mostly. The American format came from the British, who used MDY before the 20th century. Britain eventually switched to match the rest of Europe. The American colonies had already split off and kept the original convention. That's it. There's no deeper reasoning. It's a colonial-era formatting decision that persisted because nobody had a strong enough reason to change it.
DMY has the advantage of massive global adoption. When most of the planet does something one way, there's a powerful argument for just going with the flow. And honestly, for everyday use, DMY is fine. If someone asks "what's the date?" you usually care about the day more than the month. You already know it's March. You want to know it's the 31st. Day-first gives you the most immediately useful information first.
But that argument breaks down the moment you need to sort, search, compare, or store dates. And in 2026, most of us are doing at least one of those things every single day. Every filename, every spreadsheet, every database query, every folder structure benefits from a format that's both unambiguous and sortable. YMD is the only one that's both.
The Canada Problem
A quick aside on Canada, which might be the worst example on earth. Depending on the province, the language, and the context, Canadians use MDY, DMY, and YMD. Sometimes in the same document. The government officially recommends ISO 8601, but in practice it's a coin flip. If you ever want to see what happens when a country refuses to commit to a date format, look north.
What I Actually Do
I use YYYY-MM-DD for anything digital. File names, spreadsheets, notes, calendar entries. It sorts correctly, it's unambiguous, and once you get used to it, reading "2026-03-31" is just as natural as reading "March 31, 2026." It takes about a week to stop noticing.
In conversation I say "March 31st" like every other American. I'm not going to be the person who says "twenty twenty-six, March, thirty-one" at dinner. Context matters. But any time a date is going to be written down, stored, compared, or shared across borders, there's really only one choice that makes sense. And it's the one that treats dates the same way we already treat time: big to small, left to right, no exceptions.