If I recall correctly, all of our code basically was aiming for some kind of printout... (there was no other output available to us!)
If we embedded some 'debug' printing every few lines, we could see where the program left off (or alternately, went into an accidental loop...) I think that if we were optimisitic and didn't have it printing something every few lines, the only clue we got was "something went wrong -
no printout FOR YOU"...

Our class batch was once a week for a semester and I remember carting around some pretty hefty card stacks (one line of code per card, barring some fancy card-spanning stuff) but for the life of me I cannot remember what
any of those programs were supposed to do. And 45 years of coding on and off have
Invalid Link Removed anyway !