Primary Image
Photo Credit
Runawayphill
As we flip the calendar to 2025, we remember the turn of the millennium
More Like This
Time is a purely human concept.
Regarding the Y2K computer apocalypse that wasn't - a major reason was that a lot of software was patched or completely re-written in time. I know, I was in that business. A co-worker began insisting - in the early 90s - that planned upgrades to our primary business applications (think - payroll) should include 4 digits for the year. More and more business caught on throughout the 90s. Time had some nerve calling it "a ludicrously shortsighted shortcut" to use 2 digits. For a long time, computer memory really was expensive, and programmers prided themselves on inventing clever shortcuts, for this and many other details that non-programmers never think about. And how many of Time's employees wrote out all 4 digits of the year when drafting memos or writing notes for themselves? We all knew what century it was, who needed the constant reminder? Many companies (including ours) had Y2K New Year's Eve shifts of programmers on call, in case we had missed one and something DID break. There were not ZERO incidents, just few enough that they didn't get much attention - and all the pre-work was ignored or ridiculed.
Now that we are well into this century, many applications (new or upgrades) are reverting to 2 digit years, out of laziness, not necessity. I personally had an unsuccessful argument on the phone with an automated billing system in a hospital that could not comprehend, in 2018, that my mother had been born in 1918. The possibility that a human might live to be 100 years old was not anticipated.
Daylight Savings Time is another programming nightmare. I own a lot of functioning electronics that were programmed to do DST shifts according to the "old" schedule, i.e., 2 roughly 6-month periods. I have to manually re-set them like we used to do before someone figured out a clever algorithm for a computer to use (how do you expect a machine to recognize the 2nd Sunday in April?), along with all the devices that aren't important enough to have to know the exact time (ovens, e.g.). A growing number of people want to do away with the semi-annual time shifts anyway; can't wait to see what havoc THAT wreaks on all the automated systems.
I was about to reply until I read yours. This was a big deal, especially in business because so much software was written in Cobal. Many programs were still using the old language, and many programmers used the year for calculations in the past. There was a mad scramble to find retired Cobal programmers to fix all of this. And that was just one aspect of the the situation. There are many different types of Fortran that had to be patched as well as other programs. Thanks for pointing this out.
The new millennium did not begin in the year 2000, it began in 2001. Why? Simple, there was no year zero.
You forget that the Y2K bug had the tech people scrambling to put a patch on the software so the computers still worked on Jan 1, 2000. The two digits for the year were replaced by four. The problem was anticipated and addressed before it could cause problems in critical systems (such as hospitals and government systems). I remember there was a rush to add the patch before the new year. I also remember a collective sigh of relief when it worked.
Yep I sure remember everyone freaking out!



Comments