Amazon is running a Prime Day sale on July 16 and 17. Setting aside the fact that this is two separate days, neither 716 nor 717 are prime numbers. They should’ve done 7/19 instead.
Amazon is running a Prime Day sale on July 16 and 17. Setting aside the fact that this is two separate days, neither 716 nor 717 are prime numbers. They should’ve done 7/19 instead.
dd/mm/yyyy
1607 is prime
I maintain that dd/mm/yyyy and mm/dd/yyyy are stupid.
Big -> small is how we read numbers:
yyyy/mm/dd
I prefer the simple dy/my/dy/my format (with the year reversed for added ease of use). For example, today would be 14/02/70/72.
NIST and ISO have stopped responding to my emails, but I’m optimistic that the Türk Standardları Enstitüsü will eventually adopt it as their preferred standard.
I prefer the MYOWN-16080 standard of
yy/dm/md/y/y. Also the year units are randomly swapped for encryptionWhat a shitty standard. Where are the check bits? Are you using PGP?
lmaoooo and the fucking year digits are backwards 🤣🤣🤣 i knew the date and it still took me a while to figure it out
ISO8601 club
Yes, and recurring dates naturally drop the year, so MM/DD better fits that general rule.
What if we just count all the nanoseconds since 1601 and divide by 100.
I still don’t get that timestamp approach. Especially after learning how unix/linux handle it…
At least modern AD tools can automatically do the date conversions now.
Because it’s a basic data structure that holds time, instead of multiple interrelated ints…. And it’s easy to do math on.
^^ This is the only acceptable way to write out the date numerically. I’ll die on this hill.
Yes but small is more relevant since you’re more likely to know the big. therefore i propose we put minutes ahead of hours.
Big is more important than small. If your use case has the big stuff in context, drop the big.
You mean YYYY-MM-DD right? Right?!?
That would not give a prime number