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:
Beyond the Digital Gatekeeper: Strategies to Make Your CV ATS-Friendly
How much time have you spent staring at an empty mailbox after applying to numerous positions? "We'd like to confirm we've received your application…" and then… silence. Even an automatic rejection would have been more bearable. You've done everything right. You have relevant experience, a matching skill set, a well-maintained…
Liskov Substitution Principle (LSP) In IOS: How To Write Trustworthy Code?
After tackling the Single Responsibility Principle and Open-Closed Principle, it's time to explore the Liskov Substitution Principle (LSP) and how it can help us write better code. At first glance, it's straightforward: if we have a component X conforming to protocol A, and another component (Y) conforming to the same…
Ultimate Guide to Dependency Injection for Modular iOS app
Over the years, we've been told to use dependency injection to help our apps scale better. On the other hand, design patterns like MV suggest simplifying app design to the minimum, often overlooking proper dependency management. While most of us instinctively understand that Dependency Injection is crucial for maintainability, testability,…
Code Review: How to write reviews your team looks forward to?
While most people share common fears like death, public speaking, and rejection, software developers have an additional dread - receiving a bad code review. But why does a simple checkup cause so much stress and negative emotions? Is it because we fear being judged or appearing incompetent in front of…
How to Build a Dream Team: A Guide to Recruiting Great Mobile Developers
Have you ever joined a development team that was a team in name only? Torn apart by internal conflicts, petty quarrels, clashing egos, and office politics? Or perhaps you've seen a seemingly perfect candidate join a well-organized team, only to fail to integrate and quickly leave? Finding and recruiting exceptional…