Today’s events reminded me that during the Y2K frenzy, First Data basically patched all their date fields so that 2049 would essentially be the new 2000. The term “pivot year” was used to define the patch. Well, we’re half- to the pivot year and no one has done a thing to address it. Not that anybody would since in 2000 no one expected these systems, let alone First Data, to still exist in 2049. I don’t know how Fiserv solved their date issues on their multiple platforms but if they also came up with a patch like First Dara then they’re in the same boat. So, what happens next? Ignore it like we’ve done for another 24 1/2 years and gamble on being out of business or on new platforms by then, or address the situation and work on a new patch? Hint: it won’t be option 2.
6 replies (most recent on top)
Bruh you 24 years too late for that
Anyone who worked on Y2K for either platform will be long gone or d**d. No one will be around to know about the patches made to the legacy systems.
Whatever is done to resolve the 2038 problem will take care of the 2049 thing. If you were smart you would have thought of that.
Carbon Black was used successfully at Fiserv for more than a few years and it never caused an issue beyond becoming old. Crowdstrike was, with arguments, implemented over a long period of time. I departed Fiserv just after it was coming on-line. But IT is dependent on pre-testing of (generally) anything important. Microsoft did one about 8 years ago for Outlook that detonated the 2010 version around the world. Oh, a small problem not. Now that FrankServ has a good IT staff in Pune (to save costs) I have no doubt that ............
Lazy programming. What's wrong with the century coded in so you worry about this only once every 10,000 years?
LOL. Not worry about 2049 is the correct answer because most of us won’t be working there by then. Duh. 😂