How to program in C
- Rewrite standard functions and give them your own obscure names.
- Use obscure, proprietary, non-portable, compiled library packages so that you
never have to move from the platform you love so well.
- Use very descriptive comments like
/* printf("Hello world\n"); */
before each function call
- Remember - Carriage returns are for weenies.
- tabs are for those who have not reached weenie-dom yet.
- Include *LOTS* of inline assembly code.
- "User Interfaces" are for morons. "Users" have no business interfacing with
a professional product like yours.
- If you are forced to comment your code (in English), then borrow comments
from somebody else's code and sprinkle them throughout yours. It's quick,
easy, and fun to watch people's expressions as they try to figure it out.
- Remember to define as many pre-processor symbols as possible in terms of
already defined symbols. This is considered 'efficient use of code'.
How to debug a 'C' program - addendum
- Since you got it to compile, the problem must be in the Other Guys Code.
- If it's all your code then the problem *MUST* be in those unreliable Standard
Libraries. See '1.' in the previous section.
- Claim the bug reports are vicious lies meant to tarnish your sterling
reputation as a 'C' programmer (well aren't they?). After all, those who
wrote the reports couldn't even *read* your code. How could they possibly
know if there was a bug or not?
3.A] If they could read your code, review "How to program in 'C'", above.
- Claim that there wouldn't be a problem if this stingy Company/School/Wife/etc
would spring for a copy of C++.