Destructive iteration sounds horrifying but your sequences are safe.
The coexistence of ‘static’ and ‘class’ keywords is confusing. We should unify type properties and methods in Swift.
It is a common API design pattern. But how to do it in Swift is not well known.
iWatch, no. iBand and new iPod, yes. iBud, maybe.
How to use UIViewController actor chain on iOS 8 and how it is implemented.
Rules to follow when designing initializers.
Code depending on the order of view transition events is dangerous for it is so inconsistent.
How do method lookup, dynamic resolution and message forwarding work together in objc_msgSend?
Wherever delegate works block also works, but sometimes delegate is still a better choice in API design.
I found a very interesting corner case of using NSNotification, NSOperationQueue and GCD. Without precaution, I dare say 99% of experienced iOS/OS X developers would fall for it.