Open Source

Have you ever written tests? Usually, they use equality asserts, e.g. XCTAssertEqual, what happens if the object isn't equal? Xcode throws a wall of text at you: This forces you to manually scan the text and try to figure out exactly whats wrong, what if instead you

LifetimeTracker can surface retain cycle / memory issues right as you develop your application, and it will surface them to you immediately, so you can find them with more ease. Instruments and Memory Graph Debugger are great, but too many times developers forget to check for issues as they close the

Closures in Swift are extremely useful, they are interchangeable with functions and that creates a lot of opportunities for useful use-cases. One thing we have to be careful when using them is to avoid retain cycles. We have to do it so often that it begs the question: Can we

Iterating over design that needs to be reflected in code can be tedious and time-consuming. Typically the designer works in graphics editing software and then submits flat art to the developer who implements the design in code. Refining the design requires going through the same laborious process. Even harder if

Swift has very limited runtime support and no meta-programming features. I created a new tool that changes that, it's called Sourcery Using it offers many benefits: * Write less repetitive code and make it easy to adhere to DRY principle. * It allows you to create better code, one that

Even if we are writing pure Swift code in our app, we still deal with Objective-C Frameworks like UIKit. Let's take a look at how we can improve our MVVM architecture by leveraging a little bit of Objective-C runtime and Protocol Oriented Programming. Popular MVVM setup Pretty standard

As I open source another framework this week, I wanted to share few thoughts about building developer tools. Developers are lazy creatures, we like to automate stuff, we write scripts, use File Automation to get rid of repetitive work. One would think that we'd use the same principles

Many of us already write unit tests and run continuous integration servers, we can also leverage great tools like Danger to easily add some checks to the pull requests. If we'd like to prevent some common mistakes from appearing in the repo in the first place, we can