I've been working hard on the Mastering iOS Concurrency with GCD Workshop, and I've realized that there's a lot of things that we take for granted about concurrency on iOS that's not necessarily true.

Distraction has been at the forefront of my mind recently because, more so than ever, I feel like I’ve finally gotten a handle on this problem. Sitting down to do focused work was becoming very difficult. And I know I’m not the only one to feel like this either.

Last time, we looked at how to define the requests in our network layer in a way that keeps our code clean. But that was only half of the problem. Let's see how we can apply the same technique to decode our responses.

Nearly every app interacts with a server on the web, and often more than one. You’d think that we all take great care of our network layer and make sure it evolves into something robust and reliable.