The previous coalesing operations post looked at how to avoid duplicate work by combining that duplicate work into one. Here, we look at how to do that even better than before.

Bye-bye Preprocessor Macros, hello Custom Flags. Here, we look at how to switch to using Custom Flags to store configuration-specific build settings.

NSOperations are a powerful way to move work off the main thread. But just because work is undertaken on a background doesn't mean we don't care about it. Here, we look at how to coalesce duplicated work.

Constructing an effective interview process is challenging. Ask too much of candidates, and the best ones will have an offer from elsewhere before they finish your process. Ask too little and misfire on a hire. Here, we look at how to hit that sweet spot in between.

Parsing an API response into an app type is fundamental to any networked app. Here, we look at how to build a consistent response parsing approach to make that task easier than ever before.

Migrating any project from Objective-C to Swift is full of pitfalls. These pitfalls exist not just in the code itself but also the supporting structure. Here, we look at one of those pitfalls related to cocoapods.

When working with offset pagination, the page is often thrown away. Losing that content to page relationship can make merging new content into existing cached content tricky. Here, we look at how to keep the page around and simpilify things.

No one said running your unit tests on Travis CI would be easy. Who knew running tests via the Xcode UI wasn't the same as running those tests via the terminal 🤷‍♂️? Here, we look at how to prepare your test targets for running on Travis CI.

No one wants networking code scattered everywhere. Here, we look at how to utilise NSOperation to encapsulate each networking request within its own cancellable unit of work.

Everyone has a view on how to style code. None of that matters. What matters is that, as a team, you agree on the most important styles to enable developers to feel a sense of familiarity when navigating the project, regardless of who wrote the code. Here, we look at some style rules.

People don't like change. People are resistant to learn a new way of achieving the same outcome. Communication and backbone are essential to make change happen. Here, we look at how to merge teams in a way that is shaped by feedback but not held up when that feedback is unreasonable.

Splitting your code into smaller pieces is a great way to reduce the complexity of that code. It's the same for your project. Here, we look at how to extract functionality from a project into its own project, adapt it to its new purpose and integrate it back into the project from which it came.

When extracting functionality, we are often trading local complexity for communication complexity. A useful mental framework for knowing if that exraction is worthwhile is Single Responsibility Principle (SRP). Here, we look at how to extract functionality from a view controller using SRP.

Dependency injection is one of the superpowers that developers can utilise to produce code that is more predictable and easier to test. Here, we look at dependency injection - what it is and how we can utilise it.