There was this one time I remember working for a government firm. The code was a big mess and the functions themselves are hard to understand, since it was some scientific geology kind of stuff, things I wasn't keen on.
The problem was there are lots of things edited, commented out, removed, and it's generally one big convoluted piece of junk that managed to do what it was supposed to do.
This happened on my second job out of college, when really big mainframes had a megabyte of RAM, some shops were still writing business applications in Basic Assembly Language, and dinosaurs roamed the Earth.
I was hired to write programs that sucked data from tapes submitted by the company's clients and loaded it into a database. Yes, the programs were all written in BAL.
I hadn't been there long when I was assigned to modify a program written by one of the company's handful of senior programmers. He was a nice enough guy, but he had a juvenile sense of humor and an exaggerated idea of his own abilities.
When I looked at the program, I found the usual stuff: save registers; load data conversion library; open file on the input tape. Then the start of the main loop, graced with the label BACK.
BACK? I wondered. Why BACK? I assumed it meant something, but I couldn't imagine what.
I got my answer when I reached the end of the program and found a branch instruction that referred to the label BACK, with this comment:
B BACK TO THE BEGINNING AND DO IT AGAIN
"Branch back to the beginning and do it again!" Oooh! Clev-er!