To maintain our codebases for years, we must create boundaries across modules. Here's my approach to doing that with The Composable Architecture.

Let's explore couple of atypical Sourcery use-cases.

How can you leverage masking to build a captivating content reveal effect?

How often have you wanted to change some small setting in your application? Let's build a generic solution.

Why I think free sponsorship model doesn't work and I've decided to move to Sponsorware model

The year is 2040, and our newest MacBook M30X processors can compile large Swift projects perceivably instantaneously, sounds pretty amazing, right? Except, compiling the codebase is just part of our iteration cycle. Other ones include: - restarting it (or deploying it to the device) - navigating to the previous location

Exhaustivity in the context of TCA tests means every test you perform has to replicate all the actions, state changes, and effects steaming from the first trigger you want to verify. It leads to a code that has a lot of TDD anti-patterns. Let’s get into the details.

No matter how experienced we are, we are bound to make mistakes in our work. This simple fact is one of the reasons why Code Reviews have become the cornerstone of software engineering processes around the world. Part of my job is building teams and establishing best practices for them