I worked on a Y2K project in 98-99 for a major car manufacturer. They tested the ERP system for Y2K (in 1997) and it failed, in a way that would make the business fail. They replaced it via this project and the business continued to be successful without interruption.
Another company I know of simply backdated their whole system by 10 years. This worked, but unfortunately the contract cycle renegotation reminders then did not appear, and competitors took many of their contracts over the next year or so. They went out of business in a couple of years.
I implemented a new manufacturing and retail system in 1992, and we used 4 digit years. The company owner complained that they were a needless expense and annoyance and that there was plenty of time to deal with Y2K. They continued to use the system well into the 2000s.
The space shuttle never flew over New Year's eve/day as they couldn't handle a single year rollover, let alone a century. Some use cases can simply avoid the problem.
Strangely enough, a few months ago I came across the bug fix for that Space Shuttle problem. "CR 93160: Year End Roll Over (YERO) Reset. Allows in-flight reset to January 1 without an IPL and complicated procedures while maintaining a good state vector."
(IPL is "Initial Program Load", IBM-speak for a reboot.)
> It's infuriating.
I worked on a Y2K project in 98-99 for a major car manufacturer. They tested the ERP system for Y2K (in 1997) and it failed, in a way that would make the business fail. They replaced it via this project and the business continued to be successful without interruption.
Same.
I worked on multiple enterprise projects for Y2K where we advanced the dates on the customer's system and ran it so we could see the magnitude of the problems and prioritize the remediation process.
There were some things that were temporarily annoying and there were some things that were critical to the business and could not be worked around manually by throwing people at it, the system needed to be fixed.
I worked on a Y2K project in 98-99 for a major car manufacturer. They tested the ERP system for Y2K (in 1997) and it failed, in a way that would make the business fail. They replaced it via this project and the business continued to be successful without interruption.
Another company I know of simply backdated their whole system by 10 years. This worked, but unfortunately the contract cycle renegotation reminders then did not appear, and competitors took many of their contracts over the next year or so. They went out of business in a couple of years.
I implemented a new manufacturing and retail system in 1992, and we used 4 digit years. The company owner complained that they were a needless expense and annoyance and that there was plenty of time to deal with Y2K. They continued to use the system well into the 2000s.
The space shuttle never flew over New Year's eve/day as they couldn't handle a single year rollover, let alone a century. Some use cases can simply avoid the problem.