What are your favorite Swift debugging tips?
How to evaluate problem areas you see in day-to-day development to assess whether they could be solved at a scale of your team/company or the whole community?
Now that we added some structure to our TCA actions, let's add automation and convenience API's.
How often have you wanted to change some small setting in your application? Let's build a generic solution.
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction
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.
A lot has been written about improving Swift compile times, but the compiler and linker are just part of the equation that slows down our development cycle. Most projects leverage great 3rd party tools like SwiftLint, Sourcery, SwiftGen, SwiftFormat and many more. Leveraging those tools is the right thing to
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
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