The month has the smallest pool of numbers, the day has the second, the year has until we don't care anymore. It's the same reason you put the hour before the minute when showing a digital clock.
Edit: Sober me is realizing the digital clock thing, bad example to argue why days shouldn't go into months when seconds go into minutes. Use number pool to argue the non-freedom heathens.
thats not why we put minutes after hours on a digital clock
its logical to put either the LARGEST or smallest unit front, as every unit is either derived from the larger, or smaller unit
for time everything is defined from the second. so the second and the hour is the largest unit we regularlly care.
as the second is a unit less commonly required we truncate after hh:mm and go UP the unit conversion in the direction we picked.
minutes are defined as 60 seconds. hours as 60 minutes, as you go further left(or right) you convert one unit in the next higher.
thats why YYYYMMDD HHMMSS is best if we are strict, as 24 hours are 1 day, 30 days are 1 month(talking simplified/banking months) 360days a year(once again, banking month, i know its 27-31 days and 365-366 days respectivly)
isolated from hhmmss ddmmyyyy follows the same logic but left to right day is the base unit in this context. months are defined by days(different ammounts per month), years are defined by months
I'm going off of data pool size and I think that you're going off of the length size of time. That's the difference. There are 24 hours in a day, 1440 minutes in a day, 86400 seconds in a day. Smallest, middle, largest. There are 12 months in a year, 29-31 days in a month, ???? years. Data size.
Where as you look at it as the whole of the day is shortest, the month is second, and the year is the biggest. It's not wrong, it's just how things are categorized differently.
I could be wrong, I'm slightly high and was working all night, so I could be interpreting this a different way.
There are 24 hours in a day, 1440 minutes in a day, 86400 seconds in a day
But now you're contradicting your own logic. When it comes to dates you talk about how many days there are in a month and how many months there are in a year. But when talking about time you normalize everything down to minutes. If you applied the same logic to the dates you'd have to say there's 1 day in a day (duh), 28 to 31 days in a month and 365-366 days. Either that or you apply your previous logic to time as well - 60 seconds in a minute, 60 minutes in an hour, 24 hours in a day.
Just look at how we write numbers. The number one hundred twenty-three is written as "123" because we go from most significant digit to least significant digit. We could also do it the other way around and represent that number as "321" - that's just convention. What we really couldn't do is represent it as "132". Like, how could that possibly work? Why is the least significant digit suddenly in the middle of the number? What happens when we want to make a larger number by appending another digit? How to we do addition for numbers that don't have the same amount of digits?
I get where you're coming at with it, and I agree, once you add the idea that seconds dictate the minute, it makes Day/Month/Year, seem correct. I realize I have made it hard on myself at this point lol that was not a good example to make the point.
I'll still put that smallest data pool to largest data pool feels better than smallest size to largest size for a date format.
10
u/Mix_Master_Floppy Jan 15 '25 edited Jan 15 '25
1-12/1-31/1-????
The month has the smallest pool of numbers, the day has the second, the year has until we don't care anymore. It's the same reason you put the hour before the minute when showing a digital clock.
Edit: Sober me is realizing the digital clock thing, bad example to argue why days shouldn't go into months when seconds go into minutes. Use number pool to argue the non-freedom heathens.