Just adding another hard to fathom quote: > ... even using a dynamically typed language I don’t have to write the test for nil because I know that nil will nev

Just adding another hard to fathom quote: > ... even using a dynamically typed language I don’t have to write the test for nil because I know that nil will never be passed. I don’t need to make states unrepresentable, if I know those states will never be represented. It would be interesting to actually study and measure how much time even teams doing TDD spend on dealing with these kinds of errors. In my experience, they're pretty common.