Swift

Two weeks ago I've released Sourcery Pro, the most powerful Xcode extension that exists. If you still didn't check it out, you really should as it can save you 100+ hours by letting you automate a lot of repetitive code in your projects, from writing mocks

Codable is a great protocol for automating simple model persistence, but it lacks support for any kind of versioning or migrating the data from older versions. You can, of course, implement custom Codable adherence and throw in a bunch of if statements and manual decoding to achieve this goal, but

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 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

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