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

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

I've recently spoke at CraftConf about metaprogramming in Swift using my Sourcery You can watch the talk online:

I like using composition and dependency injection, but when you need to inject each entity with multiple dependencies, it can get cumbersome fast. As the project grows and you need to inject more dependencies into your objects, you will end up having to refactor your methods a lot of times,

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

I've been interviewed at Swift Coders podcast: I'm definitely investing into a better Microphone next time I'm doing any audio recording. Ben Scheirman from NSPodcast has good recommendations for affordable microphone

People use different words to classify Engineer skill, some companies give you more senior role just based on a number of years you have been working there, but what does it mean to be Senior? In this article, I composed a complete and final list of API's that