3 ms·
I know a mainframe dev who worked on y2k across a bunch of systems at the time. Asked him about it, he said that they warned management not to window the code
by JauntyHatAngle 7y ago
I know a mainframe dev who worked on y2k across a bunch of systems at the time.
Asked him about it, he said that they warned management not to window the code to 2020, and showed alternatives that would take longer to code but would be future proofed.
Most agreed with enough convincing. Some did not, usually with the argument of "the systems won't even be around in 2020!".
- legulere 7y agoJust yesterday I came across one of the places in the code are I’m working on, that pivots the y2k problem away. That place places the problem into the year 2070. That seems really far off, but the code base stems originally from the 80s.
- cgriswald 7y ago> "the systems won't even be around in 2020!". I think in many cases the thinking is: s/the systems/I/
- xmprt 7y agoIt's not right but it makes perfect sense that no one would care about building something that outlasts them unless they're super passionate about it.
- sebazzz 7y ago"the systems won't even be around in 2020!" And as it turned out in 2020 the system was still being used, but unlike in 2000, the source code was lost.