The Y2K disaster was averted by tens of thousands of programmers like me. It wasn't BS. I worked for a national financial institution and we worked 60-70 hour weeks for almost a year to avert this disaster.
True, but everything in our house, our Apple G3s and cute colorful iMac computers, bike speedometer/mileage tracker, my Casio digital G-Shocks, our digital displayed household clocks, our cordless phones... all of them, continued to display the proper date and functioned as they should on January 1, 2000. I didn’t have an “IT” department working round the clock to calibrate all of my personal devices.
Now, I understand that it was antiquated OS’s running on ancient software that was the true time bomb in the Y2K phenomenon. One of the “Big Three” entertainment companies I worked for at the time had to hire out additional IT manpower to ensure that all digital files and networks would not get corrupted. This is when I met my first “stacker/prepper.” This freelance IT guy was responsible for updating our department. He folded a dollar bill into an origami of configurations showing me all these symbolisms buried in the bills - lol it was insane. He convinced me that JFK Jr didn’t die in the recent plane crash. He was onto every conspiracy and I was eating it up!
I never did stack anything because my feeling is, if we truly get to the Wild West of things, then it’s gonna be kill or be killed and it’ll petty much be game over for a majority of the population. Fast forward to today and I truly believe that Trump and the White Hats most definitely wont let that happen.
They wouldn't have without a lot of hard work. For what it's worth, it's going to happen in 2038 for systems running UNIX derivatives including almost all Apple devices.
CORRECT. This is the best answer. My GF was a PM on one of these projects for a large insurance company, mostly mainframe stuff. The programmers were making BANK.
You are correct that most mainframe development was done in COBOL or FORTRAN running under MVS back then. However, we were coding in C & assembler on a mainframe running an obscure IBM OS called VSE for my project. FORTRAN & COBOL were supported languages, but we were trying to port the existing tape handling code that was written in assembler to C so that we could then recompile it and run it under UNIX.
This was a partnership between Microsoft and Telecheck and they put every project on hold to face the Y2K challenge. After we got past Y2K, they sold the company, and we moved everything to MVS and Unix. MVS did the tape handling and UNIX hosted the Oracle DB and the product development just like God intended. ;)
The Y2K disaster was averted by tens of thousands of programmers like me. It wasn't BS. I worked for a national financial institution and we worked 60-70 hour weeks for almost a year to avert this disaster.
True, but everything in our house, our Apple G3s and cute colorful iMac computers, bike speedometer/mileage tracker, my Casio digital G-Shocks, our digital displayed household clocks, our cordless phones... all of them, continued to display the proper date and functioned as they should on January 1, 2000. I didn’t have an “IT” department working round the clock to calibrate all of my personal devices.
Now, I understand that it was antiquated OS’s running on ancient software that was the true time bomb in the Y2K phenomenon. One of the “Big Three” entertainment companies I worked for at the time had to hire out additional IT manpower to ensure that all digital files and networks would not get corrupted. This is when I met my first “stacker/prepper.” This freelance IT guy was responsible for updating our department. He folded a dollar bill into an origami of configurations showing me all these symbolisms buried in the bills - lol it was insane. He convinced me that JFK Jr didn’t die in the recent plane crash. He was onto every conspiracy and I was eating it up!
I never did stack anything because my feeling is, if we truly get to the Wild West of things, then it’s gonna be kill or be killed and it’ll petty much be game over for a majority of the population. Fast forward to today and I truly believe that Trump and the White Hats most definitely wont let that happen.
They wouldn't have without a lot of hard work. For what it's worth, it's going to happen in 2038 for systems running UNIX derivatives including almost all Apple devices.
CORRECT. This is the best answer. My GF was a PM on one of these projects for a large insurance company, mostly mainframe stuff. The programmers were making BANK.
Were you FORTRAN or COBOL?
You are correct that most mainframe development was done in COBOL or FORTRAN running under MVS back then. However, we were coding in C & assembler on a mainframe running an obscure IBM OS called VSE for my project. FORTRAN & COBOL were supported languages, but we were trying to port the existing tape handling code that was written in assembler to C so that we could then recompile it and run it under UNIX.
This was a partnership between Microsoft and Telecheck and they put every project on hold to face the Y2K challenge. After we got past Y2K, they sold the company, and we moved everything to MVS and Unix. MVS did the tape handling and UNIX hosted the Oracle DB and the product development just like God intended. ;)