try! Swift Tokyo 2018: ​Optimizing Swift code for separation of concerns and simplicity

try! Swift Tokyo 2018: ​Optimizing Swift code for separation of concerns and simplicity

Separating concerns in code is often seen as a premature optimization when code doesn’t need to be reused, but it has huge implications in our ability to comprehend what code does. Let’s explore examples of this in Swift in what I like to call “separating what code does from how it does what it does”.

C0eafab7106ab63b8db4025e57c1a8d2?s=128

Javier Soto

March 01, 2018
Tweet