I was there, it was real. 29 at the time. I worked for one of the largest software companies back in the late '90s in their consulting practice, and there were a few Y2K howlers... In '98 I was hired as a consultant at around $2000/day to perform a Y2K audit for the company that gave me my first IT job 9 years prior. Their codebase was huge, so it was agreed that only a sampling of 3-4 different types of programs would be fully audited, such as 3-4 "C" programs, 3-4 unix scripts, etc.... The company had a sophisticated data collection system that used interactive electronic terminals in people's houses, with about 2000 terminals on-line at any one time. The entire system was time-sensitive and every bit of code seemed to require or manipulate timestamp and date data. One C program that was written in 1988 or so had a very large comment block by the developer explaining the date manipulation algorithm, only to conclude that it would not work beyond 1999 and that it "didn't matter" as the system would most likely not be in use by then! In the '80s the Year 2000 seemed like a lifetime away... One of the systems I also reviewed was a small inventory and repair tracking application that was used by the electronics tech at one of the branch offices; it was the "first" real application that I wrote for the company back in 1990 or so. Sure enough I had used the wrong database data-types and instead of storing the year component as 4 digits, it stored it as 2! When I discovered this in the context of coming back as a highly-paid consultant to conduct a Y2k audit, the company's software developer whom I was working with and I laughed so hard tears were flowing.... The audit allowed the company about 2 years to fix everything that would have failed on Jan 2000.
Another major electronics retailer in Canada that I worked with in '99 and 2000 was SAVED by their Y2K paranoia: at the end of December '99 they shut down all of their databases and systems and performed multiple cold backups to tape just in case anything screwed up in Jan 2000. Although no Y2K problems materialized, in Feb 2000 they had a massive SAN failure, knocking out major systems including e-mail. Critical retail databases had to be recovered from daily backups to keep the business running. Unfortunately, one critical inventory database would not come back online when recovered from the daily backups. It transpired that although the nightly backup job would correctly shut the database down for a backup, a member of staff had implemented a database cloning script that caused the database to be brought online during the backup window. This resulted in the daily backup for the particular database being corrupted. Fortunately for them, they had a FULL COLD backup of the database that was made at the end of December in fear of Y2K; they were able to retrieve the December backup and "roll it forward" using the archived redo logs (incremental change records). Y2K saved their inventory system from catastrophic loss...