Objective-C tip of the day

Don’t ignore warnings. If you get a warning it’s probably actually an error – things like misspelt methods (i.e. messages) which would be classed as an error in C++/Java/C# are just warnings due to the dynamic nature of Objective-C – and yet are just as bad (your method isn’t being called!)

So fix all your warnings – if the warning actually doesn’t matter – then take steps to remove it anyway so your bad warnings don’t get lost in the mix.