Joke #2553

Linux is like a wigwam: no windows, no gates, apache inside...

Gmail: Someone has signed into your account! Me: Yeah that was me Gmail: No it was on another device! Me: Yes my tablet Gmail: Someone stole your tablet?! Me: What? No! Gmail: Call the police

99 little bugs in the code, 99 bugs in the code, 1 bug fixed... Compile again, 100 little bugs in the code.

A client calls to hotline of internet service provider: "I have a problem, internet stopped working two days ago, neither I nor my son nor anyone else can access it now..." "I see, do you know what's the operating system on your PC?" "Of course, I do - it's Facebook..."

Home is where the wifi connects automatically.

Our staff has completed the 3 years of work on time and under budget. We have gone through every line of code in every program in every system. We have analyzed all databases, all data files, including backups and historic archives, and modified all data to reflect the change. We are proud to report that we have completed the "Y-to-K" date change mission, and have now implemented all changes to all programs and all data to reflect the following new standards: Januark, Februark, March, April, Mak, June, Julk, August, September, October, November, December and... Sundak, Mondak, Tuesdak, Wednesdak, Thursdak, Fridak, Saturdak I trust that this is satisfactory, because to be honest, none of this Y-to-K problem has made any sense to me. But I understand it is a global problem, and our team is glad to help in any way possible.And what does the year 2000 have to do with it? Speaking of which, what do you think we ought to do next year when the two digit year rolls over from 99 to 00? We await your direction.

How many electricians does it take to change a light bulb? Three. One to change it, and two to complain about how bad GE's customer support is.

I walked into the computer repair place with my broken Macintosh computer. I looked at the stack of them on the rack and said, ‘What’s that, Broke Mac Mountain?’

The numeric keypad only goes up to six.

There was an engineer, manager and programmer driving down a steep mountain road. The brakes failed and the car careened down the road out of control. Half way down the driver managed to stop the car by running it against the embankment narrowing avoiding going over a cliff. They all got out, shaken by their narrow escape from death, but otherwise unharmed. The manager said "To fix this problem we need to organize a committee, have meetings, and through a process of continuous improvement, develop a solution." The engineer said "No that would take too long, and besides that method never worked before. I have my trusty pen knife here and will take apart the brake system, isolate the problem and correct it." The programmer said "I think you're both wrong! I think we should all push the car back up the hill and see if it happens again."

Murphy's Laws of Computing 1. When computing, whatever happens, behave as though you meant it to happen. 2. When you get to the point where you really understand your computer, it's probably obsolete. 3. The first place to look for information is in the section of the manual where you least expect to find it. 4. When the going gets tough, upgrade. 5. For every action, there is an equal and opposite malfunction. 6. To err is human.. to blame your computer for your mistakes is even more human, it is downright natural. 7. He who laughs last probably made a back-up. 8. If at first you do not succeed, blame your computer. 9. A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine. 10. The number one cause of computer problems is computer solutions. 11. A computer program will always do what you tell it to do, but rarely what you want to do.