Tiny Swift idioms in ObjC

C macro implementations of Swift’s casting and if-let binding operators.

A list of Auto Layout DSLs, Categories, Etc.

Everyone has their own Auto Layout helpers. Here’s a list.

The problems with due-process-compatible cryptography

Over a sufficiently long timetable, we can only trust cryptography, not due process.

Why non-engineers should care about “Technical Debt”

Technical debt is an abstract concept, but it will impact your customers in tangible ways.

Why Reactive programming techniques are valuable

Reactive programming gives us better tooling to deal with mutable state.

Notes on Initialization in Swift

A collection of links and notes about initializers in Swift.

Physics in Interstellar

I was willing and ready to accept pretty much all of the science in Interstellar. But I have one big problem: rocket fuel.

Back Buttons for Web View Controllers

If Zawinski's Law applies to desktop software, then I propose a corollary for iPhone apps: every app expands until it includes a web browser. In-app browser design is something I care deeply about, mostly because everybody gets it wrong.

Real World Singleton Design

A discussion of practical architectural concerns when designing a singleton for a real-world iOS application.

Greg Titus on NSFileCoordination and Extensions

It does work, but you have to be careful.

iOS 8 Extensions Roundup

I’m excited to start using iOS 8 extensions, but it’s looking like it’ll be a rough ride for a little while.

Let’s talk about Optionals

There has been much complaining that Swift's Optional type forces you to think about whether something may be nil at every use, but aren’t we thinking about that already, just maybe implicitly? Swift’s optionals simply formally enforce the thinking we already must consider when writing (or …

Benefits of Cocoa: Still here in Swift

Until now we all agreed these were benefits of Cocoa: * C compatibility * Dynamic dispatch * Nil safety * Duck typing Now they're all bad? — Nick Lockwood (@nicklockwood) August 6, 2014 Sigh. Okay, let’s take this one item at a time: C compatibility Still there. Nil safety Was never there …

It’s Not Exploitable

This article showed an excellent point: taken alone, a memory leak or other “low-impact” bug may not appear to be much of a problem. But taken together, a set of these bugs can turn into an exploitable security hole. A few classes of bugs used in that exploit: * off-by-one * memory …

Code Optional

Part of the Project Announcements series. I realized today I didn’t post anything here announcing Code Optional. I launched this podcast in July with my friends Andrew and Kevin, two of the sharpest developers I know. We aim to discuss all sorts of topics around development, design, and shipping …