1. Forum
  2. FidoNet
  3. FIDONEWS

  • About 2s

    From Ward Dossche@2:292/854 to All on Tue Feb 15 19:08:27 2022
    February 22nd 2022 will be om a Tuesday ...

    Therefor we can say it's a 2s-day ...

    2/22/22

    --- DB4 - Feb 12 2022
    * Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)
  • From Scott Street@1:266/420 to Ward Dossche on Tue Feb 15 20:20:48 2022
    15 Feb 22 19:08, you wrote to All:

    February 22nd 2022 will be om a Tuesday ...
    Therefor we can say it's a 2s-day ...
    2/22/22

    It is also the last Y2K watch day. Those of us around for 1/1/2000 might remember the list of dates that 'might' have been trouble because crafty programmers used them to mark something other then the actual date in their programs.

    01/02/03
    1/1/1
    11/11/11
    ...
    2/22/22


    Just past trivia -- or is that trivia from the past? hmmm...



    ---
    * Origin: -={ The Digital Post }=- (1:266/420)
  • From Ward Dossche@2:292/854 to Scott Street on Wed Feb 16 12:31:52 2022
    February 22nd 2022 will be om a Tuesday ...
    Therefor we can say it's a 2s-day ...
    2/22/22

    It is also the last Y2K watch day.

    I don't remember a list such as that, but you may be right ... how about 11/22/33 ?

    When I started to work for money in IT on Jan.12 1973 we were already warned about Y2K which at that moment was still 28 years in the future and we designed/programmed already around it ...

    \%/@rd

    --- DB4 - Feb 12 2022
    * Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)
  • From Michiel van der Vlist@2:280/5555 to Ward Dossche on Wed Feb 16 15:04:47 2022
    Hello Ward,

    On Wednesday February 16 2022 12:31, you wrote to Scott Street:

    When I started to work for money in IT on Jan.12 1973 we were already warned about Y2K which at that moment was still 28 years in the future
    and we designed/programmed already around it ...

    That's not how it was everywhere.

    In 1992 I designed a special measuring apparatus for a customer. When is was finished my boss came breathing down my neck and asked what I was doing. I explained to him that I was doing some final checks on the firmware to make sure it would still work correctly after 1 jan 2000.

    2000? That is EIGHT years from now! Is it otherwise ready? I said, yes.

    Then drop the testing, and ship it so that I can send an invoice. What happens over eight years is not a poblem now.

    My boss was right. I left that company in 1996 and a year later it went belly up due to bad management. Y2K was not a problem. ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Ward Dossche@2:292/854 to Michiel van der Vlist on Wed Feb 16 16:10:45 2022
    Michiel,

    My boss was right. I left that company in 1996 and a year later it went belly up due to bad management. Y2K was not a problem. ;-)

    I remember that and I've encountered people who were like that ..."fix the problem when it presents itself"... no precautionary thinking and avoid the problem... A past prime-minister here was reknowned for that and created disasters that way ...

    \%/@rd

    --- DB4 - Feb 12 2022
    * Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)
  • From Scott Street@1:266/420 to Michiel van der Vlist on Wed Feb 16 13:20:00 2022
    16 Feb 22 15:04, you wrote to Ward Dossche:

    In 1992 I designed a special measuring apparatus for a customer. When
    is was finished my boss came breathing down my neck and asked what I
    was doing. I explained to him that I was doing some final checks on
    the firmware to make sure it would still work correctly after 1 jan
    2000.

    2000? That is EIGHT years from now! Is it otherwise ready? I said,
    yes.

    Then drop the testing, and ship it so that I can send an invoice. What happens over eight years is not a poblem now.

    Indeed! A lot of companies did this exact same logic -- "it isn't a now problem, its a future problem, ship the product and worry about it later"

    In my time preping for Y2K, we found a disgustingly large number of *commerical* applications that would have failed or given improper results post 12/31/99. The bank I worked for at the time built an entire isolated computer room to house every make/model combo we used in production with a time source that was set in the future. As we (the sysadmins and engineers) proceeded to install every OS, every version of the applications, and all the home grown apps and test them, before, during, and after the Y2K transition.

    I watched the world go to Y2K from our control room - and thankfully, without any production issues. I'm still amazed that was 22 years ago... seems like yesterday.

    Scott


    ---
    * Origin: -={ The Digital Post }=- (1:266/420)