With Swift, we get Playground that’s allows us to experiment learn. But for those of us still in Objective-C and don’t really care for the new language or can’t touch it until lucky enough to work on a new project, we now have Playground for Objective-C thanks to Krzysztof Zabłocki.
I used to joke that writing unit tests for iOS development is not necessary since there’s a compiler and laugh real hard. What I realized was that some people thought that it wasn’t a joke. Even worse, when I asked about unit tests during interviews, some candidates didn’t know how to write tests.
The root cause of this, as I see it, is that writing tests aren’t really covered at Apple’s developer documentations. And with all the new boot camps and training courses turning out iOS developers not covering testing at all, testing issue escalates to yet another level.
Here are a list of my recommendations to get started. I will create screencasts on iOS development in the future since I have more time and will ALWAYS show tests along with anything I do. Hope this helps and ping me with any questions, I’ll do my best to help.
As you may or may not know, when you send a message to nil in Cocoa, it doesn’t do anything and certainly doesn’t raise any exception. You may or may not agree with the design, but we’ve all programmed just fine with this fact.
Having said that, what if you wanted the same behavior in Ruby?
I recently had the misfortune of losing my code snippets in Xcode that was built over the years. I was able to recover some, but can’t believe that I forgot to backup properly. Yeah, talk about monumental screw up.
The snippets are located at ~Library/Developer/Xcode/UserData/CodeSnippets and that should be backed up daily. That’s what I’m now doing.
In case you’re not using snippets, then I highly recommend that you do since they’ll greatly increase your productivity. I know, duh.
I finally made the jump to use XVim. I now edit without constantly hitting escape and :wq in Xcode. Just about everything works as expected, including jumping to methods. In any case, below are the links. Installation is simple as building with with release as build in schema.