31 ;;Quote: defensive programming is bad because it hides errors that should never happen

38 ;;Quote: as you write code, look for opportunities to validate your results

39 ;;Quote: a tester reviews already tested code; programmers should not produce untested, slipshod code

77 ;;Quote: the best way to catch errors is to step through the code immediately after writing or changing the code

77+;;Quote: it is easy to simulate failures when stepping through code

77+;;Quote: step through critical code at the assembly language level

91 ;;Quote: a function interface should lead to correct code; avoid multiple returns, error values, and multipurpose functions; allow strong argument validation

98 ;;Quote: a meaningless or erroneous argument should be illegal, otherwise you hide bugs rather than find them

101 ;;Quote: write functions that, given valid inputs, cannot fail

139 ;;Quote: if you have to look up the precedence order, use parentheses to make the order obvious