That was the question I asked myself recently, when I finished optimizing Sourcery, SwiftyMocky, and tooling in Qonto’s iOS project. And it’s a qu

How one line of code led to +50% faster Swift compilation for tens of thousands of teams

submited by

Style Pass

2024-04-20 10:30:04

That was the question I asked myself recently, when I finished optimizing Sourcery, SwiftyMocky, and tooling in Qonto’s iOS project. And it’s a question that’s worth asking — just one engineer working on one open source project has the potential to have a huge, positive impact on many people.

Working in a large engineering team at Qonto, we’ve got clearly established processes, best practices and state-of-the art tools. A plethora of these tools are built using the Swift programming language — and one of these, related specifically to iOS development, is the Sourcery library built by Krzysztof Zabłocki.

At Qonto, product quality is the first priority for all teams. To drive quality, Qonto’s iOS team mostly uses mocks for unit testing, which facilitate the infrastructure of more than 15,000 tests.

Last summer (2023), we optimized mock generation by splitting a large Mock.generated.swift file. Our engineers loved this upgrade, sharing positive feedback: