Testing network requests can be tricky. Generating mock data, handling HTTP routes, etc. Thing get complicated quickly. Kakapo helps tame all that. I'm always looking for new testing tools.

The diagram on this blog post that visually conveys the new access control changes in Swift 3 is worth the visit alone.

Despite the click-baity title I thought this article looked really interesting. I have a particular passion for iterative software development. I love talking through decisions that play over how perfect can be the enemy of good enough in shipping software. It's encouraging to know that you don't need to perfect something for v1.0.0 to experience App Store success.

If you make a mistake, you would want a colleague to point it out to you, right? Just like you would hope a colleague would ask a question when they don’t understand something, and just like you want everyone on your team to speak up with ideas, even if they’re unconventional. But chances are that you’ve been in the position to speak up before and haven’t. Why? It feels like those scenarios represent a good team dynamic, but what effect do they have on a team’s performance? And how can we begin to change a team’s dynamic to improve its performance?

Even though most operators in Swift look and behave the same way they do in other programming languages, there are a few you may not know about or that behave in a slightly different manner. Bart sums it up nicely in this short article.

If you're looking for some deep discussion on error handling in Swift, this looks like the article for you. And what's more, it's only part 1.

The Speech Framework in iOS 10 provides awesome power for transcribing speech to text. Here are some SFSpeechRecognizer tips I discovered.