SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Discuss Year 2000 Issues

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Lane3 who wrote (9246)11/29/1999 11:12:00 AM
From: David Eddy  Read Replies (1) of 9818
 
Karen -

It's hard to say if these little glitches are predictive of anything. It could be that they represent date usages too trivial for the Y2K remediators to have thought of or bothered with. Or they could represent the tip of a very nasty iceberg. For now, I'm treating them as simply amusing.

My guess is that it represents sloppy work. While, as a software developer if given the choice, I would probably argue that such cosmetics should be classified as non-critical (assuming a much longer list of critical issues) & dealt with later.

And on the other hand, since such 'reports' go into the hands of the public, they do seriously undermine the carefully crafted PR message that "we're Y2Kok."

I'd like to see the media cover such stories (I assume there will be plenty more) with more depth... details of just how much work went into ensuring the critical stuff was done properly & the cosmetic stuff will be handled as time permits.

And I would think organizations sending out such documents would have enough savy (dream on!) to inspect out going documents & at least slip in a brightly colored note saying the date really should be 2000, but a printing problem caused it to come out as 1900.

If civilians get too many such bogus looking documents I assume it will seriously undermine public confidence.

- David
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext