Share Pics of People Hauling or Towing Something Wrong

[Jstpssng]

Back in the late 60s when I was a student at Purdue, a dorm buddy asked if I could pick up a printout of a program he submitted at the computer center, since I walked by it on the way to one of my classes.
Went it went to his cubby hole where the printouts and punch cards were placed, and there was a note to see the operator. Uh oh!
Went in and gave him the note, told hime i was picking it up for Rick, and he pulled out a stack of printout paper about an inch thick, and said he had a flaw in the Fortran program logic that caused a repetitive loop. He was not amused. Rick found the error and the next time, the printout all fit on one page.

Talk about thread drift!!! I had to backtrack and find out how we got to towing computer programming wrong.

 

[California]

Back in the late 60s when I was a student at Purdue, ... printout paper about an inch thick ...a flaw in the Fortran program logic that caused a repetitive loop.

BTDT. Also late 60's. It wasn't my Basic program that did it, rather, the IBM 360-20 compiler at the regional milk processing plant that ran our cards, differed from our textbook. I got back pages of the hometown bank's confidential data, their mortgage lendings.

I puzzled over my listing and found the specific line that caused it to jump into an unexpected universe. Prof gave me full credit for clearly defining the problem despite the garbage printout since my coding conformed to the textbook.

Hauling something wrong? Well the campus 'IT Professional' who daily carried our cards over and brought back the resulting printouts - for the entire campus, admin and everything, did it in his VW bug. Close enough?

 

[groundcover]

IT and towing do have similarities, " Garbage in, garbage out " !

 

[3Ts]

This has been an interesting diversion. I worked in the college's computer center while I was taking the advanced programming courses. The Halt and Catch Fire was a real instruction, although it didn't actually catch the computer on fire, it might as well have. The recovery from that was very lengthy. As for:

Went in and gave him the note, told hime i was picking it up for Rick, and he pulled out a stack of printout paper about an inch thick, and said he had a flaw in the Fortran program logic that caused a repetitive loop.

Well, there was someone who decided they needed some extra note paper and wrote an assembly language program to access the printer character controls. There is a command to slew the paper until reaching a particular channel. We did not have all the channels defined and he slewed to one that was undefined. That printer could empty a box of paper in seconds. First time we accepted that it was unintentional, the second time we required their program to be reviewed by staff before running it.

 

[Grumpycat]

Back in the late 60s when I was a student at Purdue, a dorm buddy asked if I could pick up a printout of a program he submitted at the computer center, since I walked by it on the way to one of my classes.
Went it went to his cubby hole where the printouts and punch cards were placed, and there was a note to see the operator. Uh oh!
Went in and gave him the note, told hime i was picking it up for Rick, and he pulled out a stack of printout paper about an inch thick, and said he had a flaw in the Fortran program logic that caused a repetitive loop. He was not amused. Rick found the error and the next time, the printout all fit on one page.

Back in my ancient days of say 1979 on a Sperry Univac our Fortran card stack started with a job control card which stated limits on how many $ of CPU time and pages of paper this task was allocated.

 

[lilranch2001]

Back when I still had to go to the office for work every day…… (That reads before retirement), somebody, from another location, for some reason would run some report (on the wrong printer name or they were messing with us) and it would print off reams after reams of reports that we as a user could not kill the print job.
If you could not get a hold of somebody in IT, (they were in corporate 600 miles away) you had two options, fill the paper tray enough with enough paper to finalize the print job or kill the printer and wait until somebody in IT would kill the print job and then be able to start it (the printer)back up, but in a many cases the printer was so backed up for other jobs that needed to get done…. So we did the expedient thing and just let it eat paper and toner.

We never did figure out who was running those reports and IT didn’t care enough to investigate it, and if they ever did, I never found out the answer to it.

This would happen about once a month…..

Hey, it’s only trees and dollars!

Now back to the regularly scheduled screwy trailering pics!

 

[two_bit_score]

Hey, it’s only trees and dollars!

Which is always much more important when someone else’s project is delaying mine.

 

[California]

IT and towing do have similarities, " Garbage in, garbage out " !

GIGO!

Garbage In, Garbage Out. GIGO was the name of the program that hauled posts between FidoNet and Usenet. Written by Smoky Layton.

 

[duramaxsky]

It's sticking out about 6 feet with no flag and the tie job is interesting. And the ladder rack would have held the long one properly.

 

[California]

It's sticking out about 6 feet with no flag and the tie job is interesting. And the ladder rack would have held the long one properly.

What are those 3 legged ladders used for?

We use 3-leg orchard ladders, but in ground where both feet and the third leg can be embedded. (or just as often, punched down a gopher hole.) Much more stable than a 4-leg ladder for rough ground.