Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Pastimes : The Naked Truth - Big Kahuna a Myth -- Ignore unavailable to you. Want to Upgrade?

To: IceShark who wrote (81457)	12/29/1999 1:16:00 PM
From: Cynic 2005	Read Replies (5) \| Respond to of 86076

I just talked to a friend who did a lot of cobol programming in the 80s and is now doing other things (non-Y2K related). He is 100% sure that there will be more than minor disruptions due to the non-fix of the bug. He is speaking from experience. They had about 70-80 orders which came in with a Jan 4 delivery date and the system which is supposed to have been fixed gave them Jan 4, 1900 as the delivery date. He fixed it in an hour or so but he thinks so many of hap-hazardly trained desi (a slang term for Indian) programmers with no knowledge of the system will take weeks, if not months, to fix one bug. If so many of them pop-up at a time, you get the idea. However, based on his experience at Cap Gemini and other places, he thinks that not all systems (or modules) have to be given the same top priority. Certain modules can take priority over the others to avoid rush. OTOH, he doesn;t think that embedded systems will have any problems. Basically he is of the opinion that most mission critical embedded systems don't need a date transaction. However, he acknowledged that he doesn't know much about them.