Software Jokes / Recent Jokes
A Software Engineer, a Hardware Engineer and a Branch Manager were on their way to a meeting. They were driving down a steep mountain road when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt scraping along the mountainside. The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no brakes. What were they to do?
"I know," said the Branch Manager, "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and by a process of Continuous Improvement find a solution to the Critical Problems, and we can be on our way."
"No, no," said the Hardware Engineer, "That will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip down the car's braking system, isolate more...
A Software Engineer, a Hardware Engineer and a Departmental Manager were on their way to a meeting in Switzerland. They were driving down a steep mountain road, when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt, scraping along the mountainside.
The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no brakes. What were they to do?
"I know," said the Departmental Manager, "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and by a process of Continuous Improvement, find a solution to the Critical Problems, and we can be on our way."
"No, no," said the Hardware Engineer, "that will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip down more...
A software engineer, hardware engineer and departmental manager were on their way to a meeting in Switzerland. They were driving down a steep mountain road when suddenly the brakes failed. The car careened out of control, bouncing offguard rails until it miraculously ground to a scraping halt along the mountainside. The occupants of the car were unhurt, but they had a problem. They were stuck halfway down the mountain in a car with no brakes.
"I know" said the manager. "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and through a process of Continuous Improvement, find a solution to the Critical Problems and we'll be on our way."
"No," said the hardware engineer. "I've got my Swiss army knife with me. I can strip down the car's braking system, isolate the fault, fix it, and we'll be on our way."
"Wait," said the software engineer. "Before we do anything, shouldn't we push the more...
I want to buy a software program that, when run, causes my computer to suffer grievously, though not permanently. When my screen freezes or turns blue, I want a special button I can push to make the CPU start squealing like a motherboard.
I want a device that stores an electrical charge in my telephone. For every minute I spend on hold waiting for technical support to answer, the charge would increase in intensity. When the guy from tech support finally answers, the electrical bolt of energy would be discharged into him. This should not affect my ability to hear what's going on at the other end of the line, of course. And a special function would allow the volts to double every time a tape-recorded message urges me to continue holding. "Your call is important to us," the caressing voice always claims.
I want my phone to be outfitted with a translation program which will reconstitute this irritating reminder into the truth: "Actually, we already have your money, more...
Is it possible that software is not like anything else, that it is meant to be discarded: that the whole point is to see it as a soap bubble?
Revision codes
Once you start playing with software you quickly become aware that each software package has a revision code attached to it. It is obvious that this revision code gives the sequence of changes to the product, but in reality there’s substantially more information available through the rev-code than that. This article provides a guide for interpreting the meaning of the revision codes and what they actually signify.
1. 0: Also known as “one point uh-oh”, or”barely out of beta”. We had to release because the lab guys had reached a point of exhaustion and the marketing guys were in a cold sweat of terror. We’re praying that you’ll find it more functional than, say, a computer virus and that its operation has some resemblance to that specified in the marketing copy.
1. 1: We fixed all the killer bugs …
1. 2: Uh, we introduced a few new bugs fixing the killer bugs and so we had to fix them, too.
2. 0: We did the product we really more...
My software never has bugs. It just develops random features.