This is a multi-part message in MIME format.
--===============1817825638807807218==
boundary="------------A633589EDD9775BFBB27292C"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------A633589EDD9775BFBB27292C
Content-Transfer-Encoding: 8bit
I also worked in health insurance IT around Y2K.
There appeared to be two ways to fix it. One was to extend all date fields to
accommodate the century. The other was to leave the date field as is and add
logic where it was used to "do the right thing". It was assumed that most
people were not over 100 years old so birthdays were assumed to be in the
century appropriate for someone under 100. 01/01/00 was assumed to be in 2000,
not 1900. Same way with dates of service, etc. ... assumed to be within the
last 10 years.
Still took several years to go thru all the code that had been written over the
last 20 years to get everything tested and working. All the effort turned it
into a non-event.
Note that it will probably happen again with Y2K38 when the Linux epoch date
rolls over but I am quite certain that will be somebody else's problem ;-}
On 3/17/20 10:35 AM, Mark Andy via Shop-talk wrote:
> Howdy,
>
> As someone intimately involved with Y2k back in the day...
>
> The software systems I worked on would for sure have broken with any dates >
> 12/31/1999. Now, those systems were all health insurance related, so
> unlikely to cause everything to just shut off, but I would imagine billing
> systems for utility companies issuing shut off orders for lack of payment,
> etc. etc. would also have been affected.
>
> I don't think the world would have ended, but there was legitimately a year
> or so of necessary work to make Y2k not being a thing that actually happened.
>
> FWIW.
>
> Mark
>
>
>
>
>
> One problem that we will run into is that if the
> measures are sufficiently effective, we won't have a catastrophe, and
> many people will complain, "Well, that was all for naught!" and won't
> want to take appropriate measures next time.
>
>
> Like Y2k. I'ts never been clear to me how much of the lack of
> catastrophe was due to overhype, and how much was due to a bunch of people
> buckling down and fixing it before it was a problem.
> _______________________________________________
>
> Donate: http://www.team.net/donate.html
> Suggested annual donation $12.96
> Archive: http://www.team.net/pipermail/shop-talk
> http://autox.team.net/archive
>
> Unsubscribe/Manage:
> http://autox.team.net/mailman/options/shop-talk/marka@maracing.com
>
>
> _______________________________________________
>
> Shop-talk@autox.team.net
> Donate: http://www.team.net/donate.html
> Suggested annual donation $12.96
> Archive: http://www.team.net/pipermail/shop-talk http://autox.team.net/archive
>
> Unsubscribe/Manage:
> http://autox.team.net/mailman/options/shop-talk/arvidj999@gmail.com
>
--------------A633589EDD9775BFBB27292C
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I also worked in health insurance IT around Y2K.</p>
<p>There appeared to be two ways to fix it. One was to extend all
date fields to accommodate the century. The other was to leave the
date field as is and add logic where it was used to "do the right
thing". It was assumed that most people were not over 100 years
old so birthdays were assumed to be in the century appropriate for
someone under 100. 01/01/00 was assumed to be in 2000, not 1900.
Same way with dates of service, etc. ... assumed to be within the
last 10 years.</p>
<p>Still took several years to go thru all the code that had been
written over the last 20 years to get everything tested and
working. All the effort turned it into a non-event.</p>
<p>Note that it will probably happen again with Y2K38 when the Linux
epoch date rolls over but I am quite certain that will be somebody
else's problem ;-}<br>
</p>
<div class="moz-cite-prefix">On 3/17/20 10:35 AM, Mark Andy via
Shop-talk wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAoSWGN423EQTUekipTnoP_FWcSWUT19vEdrrcO+gzwiU55CXA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Howdy,</div>
<div><br>
</div>
<div>As someone intimately involved with Y2k back in the day...<br>
<br>
The software systems I worked on would for sure have broken
with any dates > 12/31/1999. Now, those systems were all
health insurance related, so unlikely to cause everything to
just shut off, but I would imagine billing systems for utility
companies issuing shut off orders for lack of payment, etc.
etc. would also have been affected.<br>
<br>
I don't think the world would have ended, but there was
legitimately a year or so of necessary work to make Y2k not
being a thing that actually happened.<br>
<br>
FWIW.<br>
<br>
Mark</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 17, 2020 at 9:37
AM Jeff Scarbrough via Shop-talk <<a
href="mailto:shop-talk@autox.team.net";
moz-do-not-send="true">shop-talk@autox.team.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 17, 2020
at 9:33 AM Donald H Locker via Shop-talk <<a
href="mailto:shop-talk@autox.team.net";
target="_blank"
moz-do-not-send="true">shop-talk@autox.team.net</a>>
wrote:<br>
</div>
<div>Â </div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">One problem that we
will run into is that if the <br>
measures are sufficiently effective, we won't have a
catastrophe, and <br>
many people will complain, "Well, that was all for
naught!" and won't <br>
want to take appropriate measures next time.</blockquote>
<div><br>
</div>
<div>Like Y2k. I'ts never been clear to me how much of
the lack of catastrophe was due to overhype, and how
much was due to a bunch of people buckling down and
fixing it before it was a problem. </div>
</div>
</div>
_______________________________________________<br>
<br>
<a href="mailto:Shop-talk@autox.team.net"; target="_blank"
moz-do-not-send="true">Shop-talk@autox.team.net</a><br>
Donate: <a href="http://www.team.net/donate.html";
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://www.team.net/donate.html</a><br>
Suggested annual donation $12.96<br>
Archive: <a href="http://www.team.net/pipermail/shop-talk";
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://www.team.net/pipermail/shop-talk</a>
<a href="http://autox.team.net/archive"; rel="noreferrer"
target="_blank"
moz-do-not-send="true">http://autox.team.net/archive</a><br>
<br>
Unsubscribe/Manage: <a
href="http://autox.team.net/mailman/options/shop-talk/marka@maracing.com";
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://autox.team.net/mailman/options/shop-talk/marka@maracing.com</a><br>
<br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre"
wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated"
href="mailto:Shop-talk@autox.team.net";>Shop-talk@autox.team.net</a>
Archive: <a class="moz-txt-link-freetext"
href="http://www.team.net/pipermail/shop-talk";>http://www.team.net/pipermail/shop-talk</a>
<a class="moz-txt-link-freetext"
href="http://autox.team.net/archive";>http://autox.team.net/archive</a>
</pre>
</blockquote>
</body>
</html>
--------------A633589EDD9775BFBB27292C--
--===============1817825638807807218==
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Shop-talk@autox.team.net
Archive: http://www.team.net/pipermail/shop-talk http://autox.team.net/archive
--===============1817825638807807218==--
|