Up next: 2012.
:->
/johnny
I have 2 pouches of freeze dried chili left, thanks for the meal idea!
Younger programmers today, and those yet to be born, will have another Y2K-like opportunity in another 30 years or so.
I haven’t heard anybody talk about the Y10K problem.
Hey, Y2K computer systems remediation gave me a good job for a couple of years. And in fairness, there *was* a problem—although not to the apocalyptic extent North and his ilk predicted. Systems that had to do arithmetic or sorting on dates where the years were stored as two digits might’ve been glitchy and had some weird results, and there would have been inconvenience, but I seriously doubt a doomsday scenario was ever even close to possible.
As it was, most companies I knew about already had their Y2K situations handled well in advance. One large financial company I contracted with was done by the beginning of 1998; the company I worked for when 2000 rolled around was taken care of by the end of first quarter 1999.
}:-)4
Ya - why doesn’t everyone realize that all things are the same as always...each day follows the next....sunrise/sunset....nothing has changed in this country....no worries?
I recall that it was around noon and they had first reports from Australia, the announcer said “we now go direct to Sydney, Christie on your cell phone, how does it look, - Christie - everything looks fine, no problems so far -————
and her phone went dead.
I have a greater fear of BHO on 01/20/09, than I had of Y2K.
I do - I'm a ham radio operator and at the time was Emergency Coordinator for my county. We ran a statewide communications net during the evening of 12/31/99, just in case public radio systems went down.
My hamshack needed tidying, so I was cleaning and moving gear while monitoring the net. All was well until I reached to move a heavy piece of gear, whereupon I felt a twinge of pain in my lower back. The pain went away as Midnight passed, and off to bed I went.
When I awoke, I knew something wasn't right in the lumber region. It was a pinched nerve, and it kept me flat on the floor all day, watching bowl game after bowl game, like a mummy hooked on football. :)
Thus passed Y2K.
“One of the hard-core Y2K aficionados in the group actually left his wife when it came to light that she did not share his fear of the coming apocalypse”
Yeah, thats the ticket.
When I got in Y2K discussions with people I used to make them look at the expiration date on my drivers license. AZ had recently switched to DL that expired when you turned 65 which for me and most Arizonans was a date that started with 20. Then I’d say: if ADOT can handle it, which you can see they already have, what makes you think nobody can or has?
Nobody ever had an answer to that. None of them ever admitted they were full of crap after 1/1/00 passed without incident either.
It was Y2K that made me finally quit lurking, sign up on FR and make my first post.
The alarmism and just flat plain nuttiness of the Y2K posts during 1999 had driven me nearly to madness. And new year’s eve, 1999 I finally could take it no more. I signed up and posted something... spouting off about how Y2K was all a bunch of hype and nothing, absolutely nothing, was going to happen.
Mainly, I think I was merely making sure to be on record *before* 1/1/2000 so that my I-told-ya-so’s would have some shred of credibility. :-)
Granted, it wasn’t *all* hype. There were a great many systems that would have had problems, and that they didn’t is the result of some good work by lots of programmers. But the over-the-top EOTWAWKI blathering was too much.
Come to think of it, what ever happened to Jethro Tull? Not the rock band but Freeper who was posting doomsday threads here all through 1998 and 1999. After January 1, 2000, he literally fell off the face of the earth.
Y2K was very profitable for COBOL programmers like me! [Damon Wayans impression] Mo money, mo money!
This is why the gloom and doomers are so fond of “global warming,” it isn’t hindered by a pesky expiration date.
There.
Updated it. No charge.
He hadn't.