> Enforcing correctness at compile time is not the only way to insure correctness. > some prefer thinking before coding and prefer solving design puzzles Yeah

> Enforcing correctness at compile time is not the only way to insure correctness. > some prefer thinking before coding and prefer solving design puzzles Yeah, you just need to guarantee that person working on it, considered all edge cases, had uninterrupted time to think, thought about how the edge cases interact, didn't make a single mistake, wasn't sleepy, under influence of substances, and perfectly wrote it into the program without a single semantic error (off by 1). Easy. That's why I code in Malbolge Lisp CodeGen that outputs Brainfuck.