The real threat, Get a Grip!

greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread

For all those celebrating the death of glitches everywhere, let me add that 'the death of the y2k bug has been exagerated.' There was only a small chance for the major utilites to stop working due to the rollover. The hype that surrounded the date rollover now is starting to worry even TPTB. Kosky is starting to talk about its not over yet and assurances that we shouldn't be to smug. The problem is we are.

It is too late because of the attention focused on the date rollover the problems with the enterprises and their data is lost in the noise of celebrations and relief. The keys are and will continue to be oil and liquidity. Liquidity at this time seems contained and possibly a worry of too much of a good thing.

Oil will tell if any problems are local news or page one international problems. We will send in troops faster for a threat to oil than the killing of civillians. I would suggest that the major oil producers and refiners hold the key to our happiness. And any celebration ahead of the facts here is grossly premature.

Things look incredibly good and my hope is they stay that way. By the by our post y2k manufacturing system test went very well. Most computers, even P.C.'s that are very old appear to be running at least as workstations.

I would welcome any information from Gordon and further information from R.C. about oil from their contacts.

-- Squid (ItsDark@down.here), January 02, 2000

Answers

Glad to hear your production systems made it. Hope ours go as well Tuesday.

WW

-- Wildweasel (vtmldm@epix.net), January 02, 2000.


Status reports from our individual workplaces would be most interesting and informative. I hope to see a lot of them.

-- Flint (flintc@mindspring.com), January 02, 2000.

Also to add information previously posted. We saw bigger problems with data from the leap year. I will not be selling those preps until after March!

-- Squid (ItsDark@down.here), January 02, 2000.

Moderation questions? read the FAQ