> and avoid you a lot of boilerplate test. You call it boilerplate testing, I call it error checking. Of course code becomes much simpler once you stop checki

> and avoid you a lot of boilerplate test. You call it boilerplate testing, I call it error checking. Of course code becomes much simpler once you stop checking for error conditions, but it's still a terrible idea to do so (and I think Objective C silently accepting to send messages to nil is a never ending source for hard to find bugs)