Workflow

A lot has been written about improving Swift compile times, but the compiler and linker are just part of the equation that slows down our development cycle. Most projects leverage great 3rd party tools like SwiftLint, Sourcery, SwiftGen, SwiftFormat and many more. Leveraging those tools is the right thing to

If your app has a lot of content, chances are that by the time you get a chance to work on a bug report, the data that the bug appeared on will be long gone. Here are some tidbits on how I created a simple solution for that problem at

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

Writing tests in iOS apps is a touchy subject. Not everyone is so privileged to be able to write tests full-time, for different reasons. Some people have full control over their development process and choose not to write tests, maybe because they have had a bad experience with it or

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

I've found myself using Xcode a lot more than I did in Objective-C. One of things I’ve missed a lot from my AppCode setup, is the  ability to jump to specific file & line that logged a console message. Because Xcode doesn’t offer such functionality and

Playgrounds are one of the niftiest features of Swift. They allow you to quickly test out bits of code and see results in real time without going through the traditional edit-compile-run-debug cycle. "But surely playgrounds aren't possible in Objective-C?" you say... Think again. Features * Faster than