computer

SOFTWARE PROGRAM

Why computers are like men:
In order to get their attention, you have to turn them on. They have a lot of data, but are still clueless. They are supposed to help you solve problems, but half the time they are the problem. As soon as you commit to one, you realize that if you had waited a little longer, you could have had a better model.

Why computers are like women:
No one but the Creator understands their internal logic. The native language they use to communicate with other computers is incomprehensible to everyone else. Even your smallest mistakes are stored in long-term memory for later retrieval. As soon as you make a commitment to one, you find yourself spending half your paycheck on accessories for it.

How to debug a "C" program.

1] If at all possible, don't. Let someone else do it.
2] Change majors.
3] Insert/remove blank lines at random spots, re-compile, and excecute.
4] Throw holy water on the terminal.
5] Dial 911 and scream.
6] There is rumour that "printf" is useful, but this is probably unfounded.
7] Port everything to CP/M.
8] If it still doesn't work, re-write it in assembler. This won't fix the bug, but it will make sure no one else finds it and makes you look bad.

Lubarsky’s Law of Cybernetic Entomology: There’s always one more bug.
Shaw’s Principle: Build a system that even a fool can use, and only a fool will want to use it.
Woltman’s Law: Never program and drink beer at the same time.
Gallois’ Revelation: If you put tomfoolery into a computer, nothing comes out but tomfoolery. But this tomfoolery, having passed through a very expensive machine, is somehow enobled, and no one dares to criticize it.