Correct Date Format - Is this correct - 05/19/24

[Number_35]

Perhaps true; this could even be used as a test procedure. I never heard of it.
Guess where I spent New Year's Eve that year?

Several of my coworkers, all into amateur radio, spent New Year's Eve 1999 prepared to maintain critical communications for our company (electric utility) if the worst came to worst.

 

[RitcheyRch]

For my personal stuff its month/day/year (05/19/2024) but for work we use year/month/day (2024-May-19)

 

[y_p_w]

All US federal government forms I've seen specify "mm/dd/yyyy" for entry. An example would be the DS-11 passport application. That being said, they also have the expiration date on different pages (as of the current version) as "04-30-2025" or "04/30/2025".

https://eforms.state.gov/Forms/ds11_pdf.PDF

 

[y_p_w]

For my personal stuff its month/day/year (05/19/2024) but for work we use year/month/day (2024-May-19)

I keep some things (like appointments or travel) dated on my computer, and to keep them in chronological order I'll start it with the year, month, and then day, followed by a description. Today would be 2024_0520_<xxxxx>.

 

[andrew_j]

We programmers worked like dogs with the Y2K code mods. It was all hands on deck. Dates were often stored internally as YYMMDD integers for sorting purposes. Remember storage was at a premium in the explosive days of the 1980s and beyond. I wrote a ton of code fixes... Miserable and boring as cutting and stacking cord wood.

The early hack was, any stored date with year 49 to 99 was considered 1900's and 00 to 48 was to be treated as 2000's. Something like that. Luckily the IT world did not fall off the end of the world...

Y2K was biggest money grab in history. Majority of code I worked with was fine however got paid a lot to “review” code that had no issues.

Even flown to a major corporation on their corporate jet one way and fancy delivered meal to spend night to babysit servers for $250/hr and ensure they worked. They actually all were compliant.

 

[JeffKeryk]

Y2K was biggest money grab in history. Majority of code I worked with was fine however got paid a lot to “review” code that had no issues.

Even flown to a major corporation on their corporate jet one way and fancy delivered meal to spend night to babysit servers for $250/hr and ensure they worked. They actually all were compliant.

The biggest problem was many early ERP systems stored dates as strings with YY for YYYY.
Not sure if your systems had the problem.

We had coders, SMEs, and testers from the business.