let

GraphQL has been on my list of technologies to learn for a few months now, and last week I came across Majid Jabrayilov's post , feeling pretty excited to tackl…

The work of writing maintainable code is an ongoing endeavor and some of my favorite problems to solve are ones that build maintainable systems. Maintainable sy…

If you use ASCII encoding, the entire Oxford dictionary is about 5 million bytes. A single 4K image contains 25 million bytes.

Let’s explore a few ways to “bridge the gap” between the new world of async/await and other kinds of asynchronous Swift code.

Various ways to handle mismatches between how an external type is expected to be coded and the data format that an app is using.

Let’s explore how we can make it possible to call async/await-powered APIs within a Combine pipeline.

How we can now use Swift’s very convenient “dot syntax” to refer to protocol-conforming types, and how that improves some of SwiftUI’s styling APIs.

How Swift’s AsyncSequence and AsyncStream APIs can be used to build asynchronous sequences, and how they relate to Apple’s Combine framework.

How the share operator enables a Combine publisher to be reused without requiring duplicate work to be performed for each subscriber.

How to make it possible to use async system APIs on earlier operating system versions.