Joke's Database
     
Have fun searching 100254 jokes and pictures!


1. We would all have to switch to Microsoft Gas.
2. The U.S. government would be forced to rebuild all of the roads for Microsoft cars; they will drive on the old roads, but they run very slowly.
3. You would be constantly pressured to upgrade your car.
4. People would get excited about the new features of the latest Microsoft cars, forgetting that these same features had been available from other car makers for years!
5. You could have only one person in the car at a time, unless you bought a Car95 or CarNT — but then you would have to buy ten more seats and a new engine.

* Multitasking
o You can crash several programs all at once. No waiting!

* Built-in Networking
o You can crash several PC’s all at once. No need to buy Novell Personal Netware or LANtastic to crash.

* Microsoft Network
o Connect with other Windows users and talk about your crash experiences. Support groups in different cities will be organized.

* PnP
o Plug and Pray (that it works)

* Multimedia
o Experience the immense sight and sound of crashing. Compatible with existing software It will also crash your existing software.

* Increased Productivity
o You will need to *increase* your budget to buy more *products* like RAM and HardDrives. Better yet, get a new computer! That’s productivity.

* User-Friendly
o Picture of clouds

* State of the Art
o Pay for Bill’s next bid for a work of art.

* Macintosh-like
o It took Microsoft eleven years and it’s not even original.

* Online Registration
o Dial into Microsoft and let them snoop around your hard drive. This will guarantee you a place in Microsoft’s files for the rest of your life.

* MS Plus
o More money for Bill’s plus side.

* Optimize
o It will increase the utilization of your hard drive and CPU so much so that you’ll end up upgrading your system.

Once you start playing with software you quickly become awarethat each software package has a revision code attached to it. It is obviousthat this revision code gives the sequence of changes to the product, butin reality there’s substantially more information available through the rev-codethan that. This article provides a guide for interpreting the meaning ofthe revision codes and what they actually signify.

1.0:
Also known as “one point uh-oh”, or “barely out of beta”. We had to releasebecause the lab guys had reached a point of exhaustion and the marketingguys were in a cold sweat of terror. We’re praying that you’ll find it morefunctional than, say, a computer virus and that its operation has someresemblance 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 tofix them, too.

2.0:
We did the product we really wanted to do to begin with. Mind you, it’s reallynot what the customer needs yet, but we’re working on it.

2.1:
Well, not surprisingly, we broke some things in making major changes so wehad to fix them. But we did a really good job of testing this time, so wedon’t think we introduced any new bugs while we were fixing these bugs.

2.2:
Uh, sorry, one slipped through. One lousy typo error and you won’t believehow much trouble it caused!

2.3:
Some jerk found a deep-seated bug that’s been there since 1.0 and wouldn’tstop nagging until we fixed it!!

3.0:
Hey, we finally think we’ve got it right! Most of the customers are reallyhappy with this.

3.1:
Of course, we did break a few little things.

4.0:
More features. It’s doubled in size now, by the way, and you’ll need to getmore memory and a faster processor …

4.1:
Just one or two bugs this time… Honest!

5.0:
We really need to go on to a new product, but we have an installed base out there to protect. We’re cutting the staffing after this.

6.0:
We had to fix a few things we broke in 5.0. Not very many, but it’s been so long since we looked at this thing we might as well call it a major upgrade. Oh, yeah, we added a few flashy cosmetic features so we could justify the major upgrade number.

6.1:
Since I’m leaving the company and I’m the last guy left in the lab who works on the product, I wanted to make sure that all the changes I’ve made are incorporated before I go. I added some cute demos, too, since I was getting pretty bored back here in my dark little corner (I kept complaining about the lighting but they wouldn’t do anything). They’re talking about obsolescence planning but they’ll try to keep selling it for as long as there’s a buck or two to be made. I’m leaving the bits in as good a shape as I can in case somebody has to tweak them, but it’ll be sheer luck if no one loses them.

A Compaq technician received a call from a man complaining that the system wouldn’t read word processing files from his old (5-1/4″) diskettes. After trouble-shooting for magnets and heat failed to diagnose the problem, it was found that the customer had labeled the diskettes, then rolled them into the typewriter to type the labels.

1. No one but their creator understands their internal logic.
2. Even the smallest mistakes are immediately committed to memory.
3. The native language used to communicate with other computers is incomprehensible to anyone else.
4. The message, “bad command or file name,” is about as informative as, “If you don’t know what is wrong, then I’m not going to tell you.”
5. As soon as you make a commitment to one, you find yourself spending half your paycheck on accessories for it.



© 2015 ijokedb.com