Melinda Nowikowski
A
Nah, but Mr. N, who's a software engineer, had to spend the night at work in case any of the company's users panicked over something minor and called for help. We just followed the recommendations on our computers at home.
Dr. William Lester @DrWilliamLester1968
Did anybody fall for this?
04:03 PM - Dec 31, 2023
04:43 PM - Dec 31, 2023
Avatar Avatar Avatar
0
6
5
Roar Jorstad
A
In response to Melinda Nowikowski.
Damn...1999 was really hectic. I have never done so much QA and code view ever again. Convert integer dates & time to datetime datatype in the databases and make sure converted ages correctly.
04:46 PM - Dec 31, 2023
1
1
Melinda Nowikowski
A
In response to Roar Jorstad.
They weren't expecting real issues, I guess, but a panicked, paying user is at least as big a problem!
04:51 PM - Dec 31, 2023
1
0
Roar Jorstad
A
There were potential loads of overflow issues. But we didn't have too much of these, but since we had to go through everything we decided to change to datetime as well.
In response to Melinda Nowikowski.
04:53 PM - Dec 31, 2023
1
1
Melinda Nowikowski
A
In response to Roar Jorstad.
I think the company he worked for also planned ahead and did due diligence on things like that with their subscribers. The IT people wouldn't have worried, but users hear about that stuff constantly and don't understand their machines, hence potential panic.
04:55 PM - Dec 31, 2023
0
1

 

{{ notificationModalContent }} {{ promptModalMessage }}