- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Coaching Changes
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
0
Posted on 5/10/22 at 10:12 am to musick
quote:
it was coded very shitty
that is the problem. A lot of it was.
Posted on 5/10/22 at 10:17 am to SEC. 593
quote:
Reprogramming had been going on in the background for years before the public even became aware of it, about time 1999 rolled around most institutional systems had been upgraded.
Yet most knowledgeable people said it was overhyped from the beginning.
The populists and doomsday types were the ones who believed. As usual, the public overreacts to media drama.
This post was edited on 5/10/22 at 10:18 am
Posted on 5/10/22 at 10:21 am to RogerTheShrubber
Remember in the early 90s when they tried to tell us that eggs were unhealthy
Posted on 5/10/22 at 10:23 am to S
quote:
Remember in the early 90s when they tried to tell us that eggs were unhealthy
Also the MSG scare.
Big NO MSG signs at Chinese places (they were still using it, btw) and 20 years later found out its not bad for you at all.
Posted on 5/10/22 at 10:28 am to Pettifogger
My VCR from the early 90's did die that day.
That was the only electronic device I lost.
That was the only electronic device I lost.
Posted on 5/10/22 at 10:50 am to musick
Watched the Windows admins working their asses off really earning their salary (60-80 hours a week) prepping and patching. Being a Unix guy it was a total non issue as the clock wouldn't flip until 2033.
Posted on 5/10/22 at 11:00 am to musick
quote:
I have written code since 1995 yet I'm the issue and dont know what I'm talkin about?
Ok with that,
You don't know what you're talking about. Like the media in 1999, you're claiming expertise (I've written code since 1995) in a subject you clearly don't understand.
Years were input as two-digit dates. They were written on the disk as two-digit dates. They were read from the disk as two-digit dates. All operations were done to them assuming two-digit dates. No software written like this automagically new the difference between 00 and 2000.
Posted on 5/10/22 at 11:04 am to McGregor
There were a lot of legacy systems software that would have been affected by Y2K and many of those systems were written in languages no longer in vogue. Some older programmers made out very well updating legacy code. The issue was real, but it was also known well in advance, and handled.
Posted on 5/10/22 at 11:07 am to fr33manator
quote:
God it must have been clutch to be an IT guy in the kid 90s. Making bank and spooking everyone over something totally made up
Until the .com
Burst and you lost all your money
Posted on 5/10/22 at 11:08 am to musick
I remember the VP of our division had to go into the officer and wait it out incase anything happened our our clients needed us for anything. He was a single dude and beyond pissed he had to waste a NYE in the office.
Posted on 5/10/22 at 11:13 am to roberma
Hey, it gave us the classic movie Entrapment!!!!!!
Posted on 5/10/22 at 11:17 am to musick
December '99. I was home from LSU on Christmas break. My mom walks into my room and hands me a flashlight she just bought.
"What's this for?"
"When the power goes out for Y2K."
"Ok... I don't think that's going to happen, but thanks."
Y2K didn't end the world, but my bitch girlfriend broke up with me New Year's Eve a couple of minutes before midnight.
"What's this for?"
"When the power goes out for Y2K."
"Ok... I don't think that's going to happen, but thanks."
Y2K didn't end the world, but my bitch girlfriend broke up with me New Year's Eve a couple of minutes before midnight.
Posted on 5/10/22 at 11:21 am to musick
quote:
Does anyone remember the hysteria from the Y2K "bug"?
yup...telecommunications...it was a liability money grab...
all of the vendors were saying you have to have this and that to update your software and equipment...
prices were outrageous but it was all about liability...
flew me back and forth to corp headquarters for meetings on this crap...
that night the team was hold up in one of the main offices and once the clock rolled over the booze came out...
who remembers the run on banks to withdraw money...
This post was edited on 5/10/22 at 11:24 am
Posted on 5/10/22 at 11:24 am to TAMU-93
quote:
Years were input as two-digit dates. They were written on the disk as two-digit dates. They were read from the disk as two-digit dates. All operations were done to them assuming two-digit dates. No software written like this automagically new the difference between 00 and 2000.
All fixed with routine patches starting in the 1980s. these early computer people were genius, the entire premise of Y2K was that these super smart innovators "just didn't think far enough ahead" when programming. Literally smart enough to create software out of thin air to run the entire globe and solve world problems, just had a brain fart and forgot to take into account the upcoming MILLENNIUM bc it was "too far away" , right
People with any brain starting patching this a decade prior
quote:
who remembers the run on banks to withdraw money...
This is why I made the thread, I forgot about the bank stuff.
I do remember bank runs (and lines, as well as gas lines) Good one.
This post was edited on 5/10/22 at 11:31 am
Posted on 5/10/22 at 11:29 am to musick
I made a small fortune on Y2K. My company took it very serious. We started in 1998 on the changes/upgrades and continued on to 2001.
We went through millions of lines of code looking for any date functions. If it was a two digit date, it had to be changed to a four digit function then thoroughly regression tested. The source code was "C" and it was not too bad, just time consuming. The OS was UNIX. One of the problems was identifying and verifying all the various scripts and miscellaneous stuff was compliant and so forth.
I worked New Years Eve, 1999.
If our systems would have crashed, there would have been a lot of pissed off people, everywhere.
We went through millions of lines of code looking for any date functions. If it was a two digit date, it had to be changed to a four digit function then thoroughly regression tested. The source code was "C" and it was not too bad, just time consuming. The OS was UNIX. One of the problems was identifying and verifying all the various scripts and miscellaneous stuff was compliant and so forth.
I worked New Years Eve, 1999.
If our systems would have crashed, there would have been a lot of pissed off people, everywhere.
Posted on 5/10/22 at 11:32 am to musick
It wasn't a "scam", there was legit concern that some critical systems would be overlooked. After a couple decades of turnover, sometimes knowledge of the inner workings of things gets lost.
It will probably be worse in 2038.
It will probably be worse in 2038.
Posted on 5/10/22 at 11:33 am to Pitt Road
quote:
My company took it very serious
So did ours. They hired consultants who said we had nothing to worry about, so we didn't.
Posted on 5/10/22 at 11:34 am to musick
quote:
All fixed with routine patches starting in the 1980s. these early computer people were genius, the entire premise was that these super smart innovators "just didn't think far enough ahead" when programming. Literally smart enough to create software out of thin air to run the entire globe and solve world problems, just had a brain fart and forgot to take into account the upcoming MILLENNIUM bc it was :too far away" , right
Dude, two digit date codes were used because memory was extremely tight, nothing like today.
Posted on 5/10/22 at 11:35 am to musick
Climate change, covid, etc…
Page 5 of 7
Popular
Back to top
Follow TigerDroppings for LSU Football News