Third-party solutions complicate automated testing in your app. Solve this by using fakes to test external dependencies in your code. This is especially relevant to some work I was doing this week refactoring how our tests interact with RestKit, a third party library.

It's large scale adoption of Swift in projects like this that helps build confidence in the community that Swift is a "thing."

Ted Kremenek writes: “Today is July 27 — and the last planned day to take source-breaking changes for Swift 3." Woohoo, Swift 3 has some awesome changes in it and I can't wait to work with it.

No one likes a slow app, and app startup is often a users first impression of your app. Make it snappy.

Making custom test assertions in Objective-C could be a pain. But what about Swift? Follow this example to learn the simple steps to make your own.

Sometimes I fear time complexity analysis is a lost art, or at least one constrained to computer scientists. It was nice to see it put into use with some real world analysis with Swift.