computer jokes jokes

Jokes » computer jokes » jokes 12

computer jokes


problems at your end
 
 
One of Microsoft's finest technicans was drafted and sent to boot camp. At the rifle range, he was given some instruction, a rifle, and bullets. He fired several shots at the target. The report came from the target area that all attempts had completely missed the target.

The technician looked at his rifle, and then at the target. He looked at the rifle again, and then at the target again. He put his finger over the end of the rifle barrel and squeezed the trigger with his other hand. The end of his finger was blown off, whereupon he yelled toward the target area, "It's leaving here just fine, the trouble must be at your end!"

is windows a virus?
 
 
With the recent problems being encountered by Windows users all across the country, people are begin to ask themselves if windows is a virus. In response to the high demand for an answer to that question a study was done and concluded the following.

1. Viruses replicate quickly.
Windows does this.

2. Viruses use up valuable system resources, slowing down the system as they do so.
Windows does this.

3. Viruses will, from time to time, trash your hard disk.
Windows does this.

4. Viruses are usually carried, unkown to the user, along with valuable programs and systems.
Windows does that too.

5. Viruses will occasionally make the user suspect their system is too slow (see 2) and the user will buy new hardware.
Same with Windows, yet again.

Maybe Windows really is a virus.

Nope! There is a difference!

Viruses are well supported by their authors, are frequently updated, and tend to become more sophisticated as they mature. So there! Windows is not a virus.

some bumper stickers
 
 
1. BREAKFAST.COM Halted...Cereal Port Not Responding

2. <-------- The information went data way

3. The name is Baud...James Baud.

4. BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!

5. Access denied--nah nah na nah nah!

6. C:V> Bad command or file name! Go stand in the corner.

7. Southern DOS: Y'all reckon? (Yep/Nope)

8. Backups? We don' *NEED* no steenking backups.

9. E Pluribus Modem

10. .... File not found. Should I fake it? (Y/N)

11. Ethernet (n): something used to catch the etherbunny

12. CONGRESS.SYS Corrupted: Re-boot Washington D.C (Y/N)?

13. 11th commandment - Covet not thy neighbor's Pentium.

14. Windows: Just another pane in the glass.

15. SENILE.COM found . . . Out Of Memory . . .

16. RAM disk is *not* an installation procedure.

17. Smash forehead on keyboard to continue...

18. COFFEE.EXE Missing - Insert Cup and Press Any Key

19. ASCII stupid question, get a stupid ANSI!

20. E-mail returned to sender -- insufficient voltage.

21. Error: Keyboard not attached. Press F1 to continue.

22. "640K ought to be enough for anybody." - Bill Gates, 1981

23. Press any key... no, no, no, NOT THAT ONE!

24. Press any key to continue or any other key to quit...

25. REALITY.SYS corrupted: Reboot universe? (Y/N/Q)

26. Error reading FAT record: Try the SKINNY one? (Y/N)

27. Hit any user to continue.

28. Disk Full - Press F1 to belch.

29. Backup not found: (A)bort (R)etry (P)anic

30. (A)bort, (R)etry, (G)et a beer?

ten c commandments
 
 
1. Thou shalt run lint frequently and study its pronouncements with care, for verily its perception and judgement oft exceed thine.

2. Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end.

3. Thou shalt cast all function arguments to the expected type if they are not of that type already, even when thou art convinced that this is unnecessary, lest they take cruel vengeance upon thee when thou least expect it.

4. If thy header files fail to declare the return types of thy library functions, thou shalt declare them thyself with the most meticulous care, lest grievous harm befall thy program.

5. Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo' someone someday shall type ``supercalifragilisticexpialidocious'.

6. If a function be advertised to return an error code in the event of difficulties, thou shalt check for that code, yea, even though the checks triple the size of thy code and produce aches in thy typing fingers, for if thou thinkest ``it cannot happen to me', the gods shall surely punish thee for thy arrogance.

7. Thou shalt study thy libraries and strive not to re-invent them without cause, that thy code may be short and readable and thy days pleasant and productive.

8. Thou shalt make thy program's purpose and structure clear to thy fellow man by using the One True Brace Style, even if thou likest it not, for thy creativity is better used in solving problems than in creating beautiful new impediments to understanding.

9. Thy external identifiers shall be unique in the first six characters, though this harsh discipline be irksome and the years of its necessity stretch before thee seemingly without end, lest thou tear thy hair out and go mad on that fateful day when thou desirest to make thy program run on an old system.

10. Thou shalt foreswear, renounce, and abjure the vile heresy which claimeth that ``All the world's a VAX', and have no commerce with the benighted heathens who cling to this barbarous belief, that the days of thy program may be long even though the days of thy current machine be short.


Page 13 of 20     «« Previous | Next »»