There's still some weird stuff out there. I recently was helping with a Tracfone user account that has a birthyear of 1752. The support people can't fix it, apparently.

"and I believed the hype and Hysteria that they were propagating."

I remember the months of planning and long work days of recoding and recompiling and updating date input screens for 4-digit years, which would have been behind the scenes. So, I guess we did our jobs well, if you didn't even notice...I remember first noticing it with HR files, with qualified full retirement and vesting dates "not doing the math" if they passed across Dec 31, 1999. Then we had to pass everything through the update process, to turn the stored dates into 4-digit years.

We had our own code for cross-referencing the first part of a Social Security number with the location of birth on the hiring paperwork, to try to catch fraudulent IDs. Thankfully, Social Security created its own verification portal.