Is this the worst code in the world?
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
In regards to testers and, in this case, auditors... A number of years ago, I worked on an ERP application and developed auto-invoice functionality. When an item was received, and invoice would be automatically generated and approved. The auditor wanted to see the various stages on the screen... receive the item (good), generate an invoice (good), APPROVE the invoice (well... it's auto approved, so we can't show you the intermediate step...) and all of this in the production system. I convinced her to watch me perform the actions in the test system because receiving something in production would generate a cheque...
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
This is not the worst code in the world. This is just a tribute to the worst code in the world. I could not remember the worst code in the world. ;P
Kitty at my foot and I waAAAant to touch it...
-
This is not the worst code in the world. This is just a tribute to the worst code in the world. I could not remember the worst code in the world. ;P
Kitty at my foot and I waAAAant to touch it...
LOL!!!
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
Could be worse... Did you see the time that testing made a fake best-seller? http://thedailywtf.com/articles/Ive-Got-The-Monkey-Now[^]
-
This is not the worst code in the world. This is just a tribute to the worst code in the world. I could not remember the worst code in the world. ;P
Kitty at my foot and I waAAAant to touch it...
How about an undocumented testing control that was buried in the scheduler of a number of ERP systems. When ERP was a new buzzword introduced to the market, I embedded the control to enable testing and debugging of the software with customer-supplied data. That code and trigger got replicated in later versions of the system as companies purchased copies of the scheduler to speed development of their systems. When I first started working on ERP scheduling, there were only five systems on the market and I had contracts with three of the companies to tweak my original software. Every so often, I hear reports of some scheduling process going bananas and dumping screeds of garbage to whatever device is used to output from the process.
The difficult may take time, the impossible a little longer.
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
I'm pretty sure mine is the worst...
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
My recent was some RPG code that did ROUGHLY this: MINS = 'XX' of minutes IF (MINS='09' OR MINS='19' OR MINS='29'.. OR MINS='59' or MINS='99') THEN ... When I questioned this, I was told that they discovered sometimes it returns 99. To which I laughed. I suggested: MIN = 'X' of minutes (last digit) IF (MIN='9') THEN ... ... For the record, they pushed back and the code was not fixed! Fast forward a couple of years. They are no longer in business!
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
Well, I guess it could be worse... what if the "wait" had been left out? I dread to think what the load on the machine's CPU would've been like...
-
Well, I guess it could be worse... what if the "wait" had been left out? I dread to think what the load on the machine's CPU would've been like...
...although, thinking about it, arguably the worst code in the world came about as a result of an undocumented instruction in the 80286 which Intel originally included for testing. The way the instruction worked, you filled up an area in page 0 of memory with all the values you wanted all the registers in the chip to have (including instruction pointer, stack pointer, flags, etc.) and whether you wanted to run in real mode (640K) or extended mode (all the memory available) and where in the larger memory map you wanted your 640K to be... and so on - and then you could execute the instruction and the chip would cold-start in that state. The worst code in the world that I'm talking about, then, was the first version of OS/2, written for that chip, which allowed you to have one - and only one - DOS window running at any time. And - yes - IBM made that work by hooking onto Interrupt 8 (the hardware timer) and cold-starting the 80286 eighteen times a second, flipping between real mode and extended mode each time around. Horrible. Amazingly, it actually worked... I shudder to think what the chipset around the chip was thinking at the time, but there it is.
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
Rather than post the worst I've seen, yet again: http://www.codeproject.com/Messages/2227888/Re-Type-conversion.aspx[^] http://www.codeproject.com/Messages/3496420/Re-useless.aspx[^]
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
No, the worst code in the world is Programming Horror. From the original Micro Lab Data Factory database program written in Applesoft Basic. We had this nailed to the wall as a warning to others.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
No, the worst code in the world is Programming Horror. From the original Micro Lab Data Factory database program written in Applesoft Basic. We had this nailed to the wall as a warning to others.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
"If you can understand this code you're fired!" So wrong on so many levels! X|
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
-
No, the worst code in the world is Programming Horror. From the original Micro Lab Data Factory database program written in Applesoft Basic. We had this nailed to the wall as a warning to others.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
-
this was from a year or two ago...really! I was investing a batch scheduling issue using CA-Scheduler. The program in COBOL had the following code (paraphrased as I've forgotten it all). TestTime: If time <> 2am then Wait 1 second Goto testTime End If This program at the beginning of a schedule of 1,200 nightly would start somewhere usually between 11:30 and midnight because of changes to the schedule. It worked like this for 5 years before anyone challenged what was happening with the batch cycle. On review the programmer put the code in because the tester insisted on seeing the code work at 2am...there is no scheduler in developement or UAT, and of course the code never ever came out.... Once fixed the schedule dropped from 9 hours to less than 4.... Go testers!!!
-
A long time ago i was known to use something like whilst (1==1) { } then i learned to use whilst (true) { } Happy days :)
