Lest Jokes

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 more...

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 more...

Beware the lightning that lurketh in the undischarged capacitor, lest it cause thee to bounce upon thy buttocks in a most un technicianlike manner.
Cause thou the switch that supplieth large quantities of juice to be opened and thus tagged, that thy days in this Earthly vale of tears be long.
Prove to thyself that all circuits that radiateth and upon which thou toil are grounded and thusly tagged lest they lift thee unto radio heaven
Tarry thou not amongst those fools that engageth in intentional shocks, for they are surely non believers and are not longeth for this world.
Take care that thou useth the proper method when thou taketh the measure of a high voltage circuit, lest thou incinerate both thyself and thy meter.
Take care thou tampereth not with interlocks and safety devices, for this incurreth the wrath of thy supervisor and bringeth the fury of the safety inspector upon thy head and about thy shoulders.
Toil not thou on energized equipment, for if thou more...

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 more...

The Ten Commandments for C Programmers
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, more...