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.

Strategies & Market Trends : Roger's 1998 Short Picks -- Ignore unavailable to you. Want to Upgrade?

To: Pancho Villa who wrote (2033)	1/31/1998 8:52:00 AM
From: clochard	Read Replies (2) \| Respond to of 18691

I used a y2k product which I won't name, but it seemed to do what it was supposed to do: report all kinds of numbers about lines of code affected, estimates of time needed, costs, etc. This "product" took several weeks of my time to set up and run. The only problem is that these numbers are only wild guesses based on formulas, significant only to my old incompetent managers. The only thing the y2k tool helped me with was to search out the affected lines, a job done by a simple editor macro. The actual work of fixing the programs waas still the job of the programmer who had to look at each affected line (identifiable by whether it has a DD or MM or YY etc) and make appropriate changes. The biggest effort I found was to dig up the testing environment for those old programs and test them. So yes, y2k changes are dependent on teams of experienced programmers, not expensive, complicated, and useless products.