The following Dodgers have been smited by the JDK for their crimes against Jam:
All the girls! for picking on the JDK and damaging his already delicate self esteem!
The Basserd Who Nicked Copper's Stuff For the offense of nicking Copper's stuff. You are a tw*t, whoever you are and we all hope you get run over by a tram in Nottingham. Or Liverpool. Or whereever else they have trams!
Copper For the crime of playing with her Wii instead of her Jammie pals!
"Computer languages are gradually evolving to become more fool proof. Using state of the art languages is unmanly. Insist on using the oldest language you can get away with, octal machine language if you can (Like Hans und Frans, I am no girlie man; I am so virile I used to code by plugging gold tipped wires into a plugboard of IBM unit record equipment (punch cards), or by poking holes in paper tape with a hand punch), failing that assembler, failing that FORTRAN or COBOL, failing that C, and BASIC, failing that C++."
Nate that is the best site ever, rules to live by LOL. Seriously there are quite a few programs kicking about my office that follow those rules. Mostly 30 year old mainframe COBOL pieces of garbage.
Yeah, we have a bunch of COBOL and Fortran crap lurking around here too.
There is some wicked-cool advice there, e.g.,
http://mindprod.com/unmainmisc.html It's The Size That Counts It almost goes without saying that the larger a function is, the better it is. And the more jumps and GOTOs the better. That way, any change must be analysed through many scenarios. It snarls the maintenance programmer in the spaghettiness of it all. And if the function is truly gargantuan, it becomes the Godzilla of the maintenance programmers, stomping them mercilessly to the ground before they have an idea of what's happened.
I started life as a cobol programmer, the place I worked in, the bosses sacked some young dude cos he thought he was being dead funny by naming his paragraphs: