Comment The real Y2K scam... (Score 4, Insightful) 134
As someone who was working in I.T. well before Y2K (note the 4-digit Slashdot ID) and who worked on actual code and system remediation projects for Y2K, I can assure you that it was NOT a technical scam. We had old billing systems (think: AOS/VS II hosted COBOL, other dusty old crap like that), along with untold Oracle back-ended applications, which were both critical for a multi-million dollar company's billing cycle yet also poorly written enough that they absolutely 100% would have produced incorrect output starting in 2000. All of that had to be gone through with a fine tooth comb and fixed, which we did, and as a result my own Y2K on-call was as boring as hell....precisely because we'd done all that work. Other companies had similar Ancient Horrors lurking on their data center floors, and all those had to be fixed or replaced too. Never doubt the need, or underestimate the work required to get it all done.
Now, all that being said, there WAS an actual Y2K scam, but it wasn't a technical one: Rather, "Y2K Remediation" budgets became the dumping ground for all the bad ideas, lost projects, failed acquisitions, questionable purchases, mistress payments, and other C-level executive idiotic decision making. No shareholder would question the need to fix the actual Y2K problems, especially given the overwrought news cycle around that messaging. As such, C-types took the opportunity to bury all their mistakes in that budget, never to be seen again. I saw it happen with my own eyes, but nobody outside really grasped what all they were doing.
THAT was the real scam of Y2K, not the actual technical issues that needed to be fixed.