You know, there was a reason that "Y2K" was a non issue. It's because there were a lot of people working on things like code fixes, BIOS updates (well, not enough of those), and other less than glamorous projects. I was only a Net Admin at the time, tasked with finding all the non Y2K computers on the network. There were many, and some were replaced, while others were just gotten rid of since they really didn't serve their original purpose.
I don't recall "the end of the world as we know it" hype, probably because I was too busy working to alleviate the fears of those who did fear the worst.
Latest management headlines from Network World:
Browser war redux, patch time, iPod news
IT hiring to rise, but only slightly, study says
What are Cisco's top network-management challenges?
IBM aims to boost BPM skills pipeline
Surgient upgrades flagship software to automate virtual resource provisioning - Network ...
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Y2K averted
Y2K was one of the few foreseeable major situations in human history actually predicted and prevented. Nonetheless: