10 Rules for Writing Safety Critical Code

http://spinroot.com/p10/

1 Restrict to simple control flow constructs.
2 Give all loops a fixed upper-bound.
3 Do not use dynamic memory allocation after initialization.
4 Limit functions to no more than 60 lines of text.
5 Use minimally two assertions per function on average.
6 Declare data objects at the smallest possible level of scope.
7 Check the return value of non-void functions, and check the validity of function parameters.
8 Limit the use of the preprocessor to file inclusion and simple macros.
9 Limit the use of pointers. Use no more than two levels of dereferencing per expression.
10 Compile with all warnings enabled, and use one or more source code analyzers.

>>9

Also, job security is often fixing and improving C/C++ code.

Haskell is a simple and understandable language for normal people like physicists and mathematicians, cleansed of the byte-sodomy, and it makes specially-bred computer programmer-lametards unnecessary. Yes, you've heard that right. Once this language for normal people becomes widespread, the byte-Sparta of warrior programmer faggots tempered by being assfucked with the von Neumann architecture and fucked in the mouth by the applicative order will lose its raison d'etre. What will they do then, these pathetic subhumans who have had everything human washed out from their heads for five years in coding school? The only thing remaining for them will be ceasing their wretched existence.