Programmer Jokes / Recent Jokes
A Engineer and an Programmer are sitting next to each other on a long flight from LA to NY. The Engineer leans over to the Programmer and asks if he would like to play a fun game. The Programmer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Engineer persists and explains that the game is real easy and a lot of fun. He explains "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Programmer politely declines and tries to get to sleep.The Engineer, now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!" This catches the Programmer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Engineer asks the firs t question: "What's the distance from the earth to the moon?" The Programmer more...
Once a programmer drowned in the sea. Many Marines where at that time on the beach, but the programmer was shouting "F1 F1" and nobody understood it
University of Alaska
Statewide Dept. of Human Resource Development
303 Tanana Drive, Room 1, Bunnell Bldg.
Fairbanks, Alaska 99701
Sirs,
I've decided to apply for your position as a systems
programmer even though I hate snow worse than I hate snakes.
I've been training for going on two years now at a local
community college in data processing, computers, and that sort of
stuff and have probably learned all about MVS/SP, JES2, ACF/VTAM,
NCP, CICS, IDMS and a bunch of other letters you didn't even list
(In fact, there's about 26 of them total)!
I feel that this qualifies me in that respect. As for IBM
systems, I have an IBM Selectric and even an IBM wall clock at
which my current boss says I watch better than anyone else here.
You list Assembly but that seems like a typo to me because that
is a hardware thing, nothing real programmers are supposed to do.
However, if you will train me I will even buy my own more...
- Real Programmers don't write specs. Users should consider themselves lucky to get any programs at all and take what they get.
- Real Programmers don't comment their code. If it is hard to write, it should be hard to read.
- Real Programmers don't write application programmers, they program right down on the bare metal. Application programming is for feebs who can't do systems programming.
- Real Programmers don't eat quiche. Real Programmers don't even know how to spell quiche. They eat Twinkies, Coke and palate-scorching Szechwan food.
- Real Programmers don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much it did for them.
- Real Programmers don't read manuals. Reliance on a reference is a hallmark of the novice and the coward.
- Real Programmers don't use FORTRAN. FORTRAN is for wimpy engineers who wear white socks, pipe stress freaks, and crystallography weenies. They get more...
Programmer at this retail chain gets an assignment to add some functionality to four reporting applications. One change request is to add passwords to one of the four applications -- but just one."Just doing one sounded suspicious to me," says the programmer. "So I decided to code the password logic in a separate module for easy reuse. I only had to add one line of code to the existing executable."Fast-forward six months: The new versions are installed in a handful of stores for beta testing before they'll roll out to 1,000 stores nationwide. Programmer's boss drops by his cubicle to tell him that the users like the password function, but they wanted it on all four applications. How long would it take to add it to the other three?He calculates: add one line of code, compile, do some testing. That's maybe a few hours' work if everything goes as planned -- which it seldom does."Two days," he tells his boss.She's skeptical. "Are you sure?" she more...
Programmer produces code he believes is bug-free.
Product is tested. 20 bugs are found.
Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
Repeat three times steps 3 and 4.
Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
Users find 137 new bugs.
Original programmer, having cashed his royalty check, is nowhere to be found.
Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
Original programmer sends underpaid testing department a postcard from Fiji.
Entire testing department quits.
Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
New CEO is brought in by board of directors. He more...