Clean code, S.O.L.I.D., testability, abstractions, separation of concerns, etc.
These and other important iOS / Swift development good practices
explained simply and with memes 
Clean code, S.O.L.I.D., testability, abstractions, separation of concerns, etc.
These and other important iOS / Swift development good practices
explained simply and with memes
Recent Posts:
How to implement universal networking module in Swift (pt.2)
Let’s pick up where we left off! So far in part 1 we’ve discussed how to make a universal and robust networking client. Now, let’s take a look at how we can make it even better. Arguably, the most important feature of any universal tool is extendibility. We cannot account…
How to implement universal networking module in Swift (pt.1)
What’s the first service you usually implement in an app? It’s either networking or storage, right? And when it comes to networking, what are your choices? Most people either operate on URLSession directly, leveraging its multiple APIs, or add a 3rd party library like Alamofire. But there is also a…
Why should you KISS your SwiftUI views? Explained with memes
What are KISS SwiftUI Views? If you’ve been a software developer long enough, you’ve surely heard about the Keep it Simple, Stupid (KISS) design pattern, right? It states that we should implement our systems the simplest way possible across all the application layers: persistence, services, business logic and the UI. …
App analytics – done the right (memical) way
A story of our lives… Imagine wrapping up an iOS app with only one feature left to implement: the analytics. The client’s marketing team chose a well-known framework that should be easy enough to integrate. They even provided you with a document describing which user actions to track! Nice. It…