I meant it doesn't complain when sending a message to a nil object though this is probably not what you intended and makes tracking down bugs harder... or maybe I just have C++ mindset.
The trick is to use null checks almost like you're writing C++, but drop them when they are unnecessary and inelegant. Convince yourself that a null check is unnecessary before removing it. This way you're reducing the chance of bugs and making them easier to pinpoint.
For example, you can do:
if ([someArray count])
if (someArray && [someArray count])
[[someArray lastObject] dance];
tl;dr: Messaging nil is not idiot-proof but it makes code read better.
NSString *myString = nil;
if ([myString compare:@"something"] == NSOrderedSame) {
...
}