If this question has been addressed previously, please excuse my post.

There was reported from many sources, the speculation that a certain percent of errors would be introduced into code from the remediation process itself. X number of errors per X000 lines of code. It appears (initially anyway), that (A) these errors must have not been a significant problem in the first place, or (B) are in process of being fixed as they are incountered, or (C) we have yet to see the full effect from these errors at this time.

I think it is fair to say that programming errors in remediated code are a common occurance, therefor their impact on the functionality of the rest of the code, is the point to address.

My question then, is where do we stand at this time with regard to these remediation code errors?

KT

-- K Taylor (KTaylorOre@webtv.net), January 07, 2000

Answers

Ktaylor......Give it some time, Patience is a virtue

-- kevin (innxxs@yahoo.com), January 07, 2000.

We should all pray as hard as we can so that God will grant us at least SOME errors. Then we won't feel so stupid.

-- Pray for Errors (doomer@crossedfingers.com), January 07, 2000.

Amen, brother.

-- (squirrel@huntr.com), January 07, 2000.

These are errors that will show up after the remediated code is put into production. Depending on their severity, they will be handled they way software errors are handled now - if the system crashes, some programmer will have to figure out what went wrong. If bad data is produced, auditors may catch it, or people will get charged or paid the wrong amount, and will complain, and a programmer will have to fix things. This is probably happening now, because that is life in corporate data processing.

If databases are corrupted they way Cory Hamasaki thinks they will be, the company may permanently lose valuable data, and will be less productive or may be driven out of business. If the latter possibility happens, you won't know about it until the company announces losses and its stock crashes, or the owner of the company commits suicide. Chances of this happening are very slim.

The big test will be when you get your January bills from the phone company, the gas company, etc., and when Social Security sends out January's checks to retirees.

-- kermit (colourmegreen@hotmail.com), January 08, 2000.

Worked for 2 years on a Y2K remediation team. I'm a systems person, so I was involved with the testing of all our apps. What was amazing to me, and to many others I ineteracted with, was the fact that the programmers did not have to make that many changes to their code. I'm not saying there were NO Y2K fixes needed, just far fewer than we imagined. Far fewer lines of remediated code are in place than the numbers being tossed about.

We were expecting a lot more corrections to be required than actually were. So, while there is a danger the remediated code could have bugs its not as bad as it seems because the fixes were minor and few in number. Also, there was extensive re-testing after the code was repaired.

-- Chris Josephson (chrisj62954@aol.com), January 08, 2000.