Programmers That Plants bugs and those that don't care?greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
Dear Forum Folks:
I really want to be serious about this posting. AS many of you may know That I am now a 10 on the scale. All the hipe about this thing being a bump in the road on our way to the next century. I know many of you are business people as I am.for now. I know many of you have hired experienced and see work all the time that is done by experienced charactors. Some of it would not pass a test if a grade school kid was giving the inspection.
With all the embedded chips out there that is lost or unreachable that is more than enough to tell me that this thing will not be over anytime soon. It will take months to find the bad embedded chip if one is neded to be replaced. If its in space more time is needed, and if its under the ocean, the ocean has to have miles and miles of wires and chips. The same if it turns out to be underground in a pipeline or some other underground box.
Now in addition to that as I have mentioned above some people just won't do their job right no matter how much they are paid. Some are just lazy, other will say that should be good enought to work and move on to another area. Then you have mondays hangover feelbad days, coffee breaks, toilet reading breaks,and the clock watchers. Y2K is no different from any other job, except it is boring as hell. That worries me about banks, utilites, railroads, transportation in general.
The other thing that really worries me is that bad bugs may be planted intentionally by grudge holders, terrorist haters of goverment corporations and many other reasons. Then we have the hackers that love this type of stuff.
If all the work could be and was finished by 12/31/99 even so how many mistakes were made by programmers and other mistakes made by companies supplieing those fixes. And how long to fix?
I figure that fixing all these computers would be with me taking all the programmers thats now working and going into a one acre building and finding a whole warehouse of 2 feet wires with different end, But all the ends will fit only into the right end of the right wire and you have to hunt that wire down put them together and then connect them before everything will work around the world. Did I say they had 24 months to get this done.
That how I am figureing out how all this might be working out.
I am not a programmer, But I do know when a tube is hot the connections are broken. Computers are way mor complicated than that.
BY the way some cities aned towns don't even have programmers that can work on the y2k problem due to not being trained in certain area of coding.
I'll let you rest for a while since I won't be posting for a while.
-- L.Brock (Lon email@example.com), February 28, 1999
Another thing bugging me is the virus threat. I wonder how many "unknown" viruses are out there with a trigger date of 1/1, just to throw another monkey wrench in the works, and make the day even more interesting? <:)=
-- Sysman (firstname.lastname@example.org), February 28, 1999.
Thanks. I needed that.
Yet another thing to think about. There are indeed people out there who will help tear down an already shaky system just for "fun".
More beans. More rice. A hundred pounds of lentils.
Moving to the country.
-- Jon Williamson (email@example.com), March 01, 1999.
I am working on a "cool" non-Y2K program, so I'm doing the best I can. Straightforward programming. I know very little about viruses and time-bombs.
It has been mentioned on this forum (rather, a question) about the possibility of drafting programmers for Y2K work. That will never happen because while most government people are assholes, not all are stupid and someone would realize that unwilling programmers could cause all sorts of havoc. I know that I myself would undertake a fast course in self-teaching myself about viruses, just as I have every other computer subject I've learned. I'd actually love to be drafted to work on IRS computers. Heh-heh :)
BTW -- the reason my "domain name" has changed from MicroSoftSucks.com to MicrosoftAndIntelSucks.com is that Intel's new Pentium III processor has a unique identifier in each chip, so the particular machine using it can be identified remotely. I think this ties in with MicroSucks' announced policy that all Windows 2000/Office 2000 products be registered with them, otherwise they will not function. The Intel ID would allow MicroSucks to verify on-line that the specified Microsucks serial number software was being used on only the specified Intel "powered" computer.
But, good news -- AMD K6 outsold Intel recently. Boycott Intel. Buy AMD or Cyrix.
-- vbProg (vbProg@MicrosoftandIntelSucks.com), March 01, 1999.
vbProg - I thought we learned recently that the government people at the Defence Department have indeed been stupid enough to hire programmers without adequate security checks.
-- Brooks (firstname.lastname@example.org), March 01, 1999.