<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Radu Dan on Medium]]></title>
        <description><![CDATA[Stories by Radu Dan on Medium]]></description>
        <link>https://medium.com/@radu.dan.ext?source=rss-72f6dd0d38e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7HzFRdO6kh4k0TnA0-UrdQ.jpeg</url>
            <title>Stories by Radu Dan on Medium</title>
            <link>https://medium.com/@radu.dan.ext?source=rss-72f6dd0d38e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:15:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@radu.dan.ext/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Xcode Migrations: From Stone Age to AI Mastery]]></title>
            <link>https://medium.com/qonto-way/xcode-migrations-from-stone-age-to-ai-mastery-d2590657e809?source=rss-72f6dd0d38e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2590657e809</guid>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Radu Dan]]></dc:creator>
            <pubDate>Wed, 27 Aug 2025 14:34:43 GMT</pubDate>
            <atom:updated>2026-03-20T16:16:53.778Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h0XR4IJY0eI-Ev2bSlq6-g.png" /></figure><blockquote>How we transformed three-week migration nightmares into one-day automated processes that don’t disrupt anyone’s work</blockquote><h4>Introduction</h4><p>Every iOS developer knows the dread of Xcode migrations. What should be a routine update turns into weeks of chaos, broken builds, and frustrated teams. At Qonto, with 60+ iOS engineers and tens of thousands of tests, these migrations used to paralyze our entire development process.</p><p>This is the story of how we turned our biggest pain point into a competitive advantage.</p><h4>The migration hell we used to live in</h4><p>You come to the office with your coffee in one hand and your laptop in the other, ready to finish your feature. Those last two bugs were hard, but you finally found a solution and can almost taste that sweet victory of shipping your code.</p><p>You open your MacBook and see a Slack message: <em>the new Xcode migration has been completed. The codebase now requires the new version of Xcode</em>.</p><p>Wow! That was unexpected.</p><p>You scramble to download the new Xcode, wait ages for it to unzip, then encounter simulator runtime issues. You clear caches, delete derived data, install iOS runtimes, and restart your machine. But it’s noon already.</p><p>Your local environment is in chaos. You constantly switch between Xcode versions while maintaining ongoing work. Later, you encounter this dreaded error about “compiled module was created by a different version of the compiler.”</p><p>After reading StackOverflow threads, you discover the framework was compiled with the previous Xcode version and you’re trying to run the app with the new Xcode’s different Swift compiler.</p><p>Each external dependency needs verification — not all are compatible with the new Xcode immediately. You face several critical dependency management issues:</p><ul><li><strong>Cache synchronization</strong>: Your local cache getting out of sync with repository versions</li><li><strong>Missing artifacts</strong>: Forgetting to upload compiled frameworks, causing build failures</li><li><strong>Rebuild overhead</strong>: You and every other developer rebuilding dependencies locally when switching Xcode versions</li></ul><p>This local-only approach meant each developer had to rebuild binaries locally when switching Xcode versions. And that took hundreds of years.</p><p>Beyond individual developer issues, there’s the team dimension: CI/CD challenges, infrastructure instability, resource consumption spikes, and configuration conflicts.</p><p>Before adopting <a href="https://tuist.dev/">Tuist</a> to generate our project, and cache our modules, we constantly dealt with .pbxproj merge conflicts across 60+ iOS engineers.</p><p>A few years ago, <strong>half of our Xcode migrations took more than three weeks</strong>. That’s <strong>ONE</strong> person every day trying for at least 8 hours to fix issues caused by the new Xcode. <strong>FOR ALMOST ONE MONTH!</strong></p><p>This happened for minor version updates, not just major releases. Development workflows hit bottlenecks. People cut corners: commenting out tests, removing flaky UI tests, or skipping them entirely, leading to quality drops.</p><h4>The Kaizen Spirit</h4><p>It was time to improve.<br>What’s a “Kaizen”, you might ask? Is it a dish? No!</p><blockquote><a href="https://en.wikipedia.org/wiki/Kaizen">Kaizen</a> is a Japanese term meaning continuous improvement — a mindset that dramatic positive change is possible through small, continuous steps. It empowers individuals to challenge the status quo, eliminate waste, and take responsibility for improving their daily work, turning each improvement into a learning opportunity.</blockquote><p>One day, we said, “Enough is enough!” Instead of accepting that migrations will always be painful, we decided to systematically eliminate waste and improve our process.</p><p>When something annoys you in your daily work, you have the time and the right to fix it. It’s about taking ownership of the frustrations in your daily work and systematically making them better.</p><h4>Strategic architectural change: removing CocoaPods</h4><p>One of the most impactful decisions in our migration journey was <strong>completely removing CocoaPods</strong> from our project. This strategic architectural change fundamentally transformed our migration complexity.</p><p><strong>Before</strong>: We maintained dual dependency management systems (CocoaPods + SPM), each with different caching strategies, build processes, and failure modes. Migrations required updating both systems, managing precompiled binary compatibility across two different frameworks, and debugging issues that arose from their interaction.</p><p><strong>After</strong>: Moving to Swift Package Manager exclusively eliminated:</p><ul><li>Binary cache synchronization issues between different dependency systems</li><li>Dual build processes that needed separate migration paths</li><li>Complex interactions between CocoaPods’ Ruby-based tooling and SPM</li><li>Precompiled binary management overhead for CocoaPods dependencies</li></ul><p>This wasn’t just a technical cleanup — it was a strategic decision that <strong>reduced migration complexity</strong> and enabled much of the automation we built later.</p><p>You can read more about our modularization journey <a href="https://medium.com/qonto-way/modularization-72f2838d2ee7">here</a> and <a href="https://medium.com/qonto-way/choosing-the-right-tool-to-modularize-our-ios-codebase-869a8ef568b8">here</a>.</p><h4>Tracking new Xcode releases</h4><p>We wanted to know when new Xcode versions dropped so we could be prepared.</p><p>How can we do this without refreshing Apple Release notes every day? An email sent to us? No, we hate emails. An SMS? Too intrusive. A Slack message offering details about the new Xcode? Perfect.</p><p>So we built exactly that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*84VfWTgMvh4h6QkIwaai8w.png" /><figcaption><em>The abstract/simple high-level diagram of our Xcode releases tracker</em></figcaption></figure><p>We love Swift. Why not write our Xcode Release Checker in Swift?!</p><pre>public struct GetCurrentXcodeVersionUseCase {<br>...<br>    public func execute() -&gt; String? {<br>        guard let rootURL = repository.path(of: .root) else { ... }<br><br>        return repository.readFile(<br>            from: rootURL.appendPath(&quot;.xcode-version&quot;)<br>        )?.trimmingCharacters(in: .whitespacesAndNewlines)<br>    }<br>}</pre><p>The use case from above fetches the current Xcode version that the project uses by reading the information from .xcode-version, a file stored in our repository which gets updated with the current Xcode version.</p><p>Finally, everything is assembled in the main function which is fairly easy to read.</p><pre>// main.swift<br>func run() async throws {<br>      guard let currentXcodeVersionNumber =  ...<br>          shell.print(color: .red, text: &quot;Error while reading the current Xcode version.&quot;)<br>          return<br>      }<br>      let xcodeVersions = try await fetchXcodeVersionsUseCase.execute(api: api)<br>      guard let latestStableXcodeVersion = getLatestXcodeStableVersionUseCase.execute(<br>          xcodeVersions: xcodeVersions<br>      ) else {<br>          shell.print(color: .red, text: &quot;Unable to find the latest stable Xcode.&quot;)<br>          return<br>      }<br>      guard let latestBetaXcodeVersion = getLatestXcodeBetaVersionUseCase.execute(<br>          xcodeVersions: xcodeVersions<br>      ) else {<br>          shell.print(color: .red, text: &quot;Unable to find the latest beta Xcode.&quot;)<br>          return<br>      }<br><br>      sendMessage(...)<br>}</pre><ol><li>We get the current Xcode version.</li><li>We fetch the latest stable Xcode version.</li><li>From the API response, we pull out the required information about latest beta.</li><li>We create the sanitized message and send it to Slack via fastlane action.</li></ol><p>The Fastlane action is straight forward:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*_-uUD6zUCM7vFflKNtMc8A.png" /><figcaption><em>The Fastlane action that sends the Slack message</em></figcaption></figure><p>We use a dedicated channel to post our messages and everything is triggered by our CI schedule:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*6eTpabY2Ma2ph1pvKt717g.png" /><figcaption>Bitrise schedule</figcaption></figure><p>As we tested the recurrence of the schedule, we discovered that once per week is enough for us.</p><p>The schedule calls the Xcode Release Checker tool:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*kdLCRzB21WqRGp6L2X3qvw.png" /><figcaption><em>The tool that gets triggered from Bitrise</em></figcaption></figure><p>Hooray! We integrated an automated monitoring system that allowed us to anticipate new Xcode releases. This system was fully integrated with Slack and gave us a nudge about betas as well.</p><p>We were prepared.</p><h3>Communication that actually works</h3><p>It was time to put our improvements into practice. We did a couple of Xcode migrations, and we wanted to know how the team felt about them.</p><p>We sent the team a Google Form asking them about the process. Overall, the feedback was positive, but a couple of answers caught our attention.</p><p>For one third of our people, it wasn’t clear what they had to do when someone announced a migration of the codebase to a newer version of Xcode. About 25% of the people did not understand what we did and why.</p><p>That was clearly a problem. It seemed that our messages were not propagated well to the team.</p><p>We established a multi-phase communication strategy with standardized message templates:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*LxwFqdbDqlEsoyLTCurVEg.png" /><figcaption><em>Message template when we were started a migration</em></figcaption></figure><p>We created:</p><ul><li>A subscription calendar for key migration dates</li><li>An Xcode migrations portal with Q&amp;A and troubleshooting sections</li><li>A visual timeline showing the 5-day migration process</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhyjZvQFtAWwJND2yJuQ6w.png" /><figcaption><em>Timeline of Xcode migrations</em></figcaption></figure><p>After implementing these communication improvements, we flipped the results — over 90% of people were clear on what they needed to do once an Xcode migration was announced.</p><p>Good times! 🎉</p><h3>Automation</h3><p>Even after removing manual steps, we spotted more automation opportunities. The outcome was a friendly CLI buddy that actually helps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*45092xlVcqZVmaLEKalGDg.png" /><figcaption><em>CLI Xcode Migrations</em></figcaption></figure><p>Our Swift-based CLI automates the migration process by:</p><ul><li>Creating a dedicated migration branch</li><li>Cleaning build artifacts and dependency caches</li><li>Updating the .xcode-version file to reflect the new version</li><li>Rebuilding and committing updated binaries</li><li>Running validation scripts to ensure successful compilation</li><li>Performing routine checks that previously required manual verification</li></ul><p>We managed to create custom migration scripts (all in Swift, of course). These were integrated with our Makefile system using commands like make qonto_app and fully worked with our repository.</p><p><a href="https://medium.com/qonto-way/choosing-the-right-tool-to-modularize-our-ios-codebase-869a8ef568b8">By adopting Tuist</a>, our codebase became more mature. It is modularized, and we finally got rid of those problematic merge conflicts, allowing us to focus on things that matter.</p><h3>The real test: an Xcode major</h3><p>We had an important test: migrating to Xcode 16.</p><p>Following our structured approach, we allocated one dedicated person for the migration, supported 50% by a Staff engineer, with two main objectives:</p><ol><li><strong>Zero delay for ongoing projects</strong> (business continuity)</li><li><strong>Target scope: 2.5 weeks</strong> (full codebase using Xcode 16 quickly after stable release)</li></ol><p>We created a database for each external dependency and started early with testing Xcode betas.</p><p>Early beta testing was vital to discover problems like:</p><ul><li>NSDecimalRound crashed the app built from Firebase</li><li>3000+ snapshot tests failed without noticeable pixel differences</li><li>Collection view cell dequeueing changes broke acceptance tests</li></ul><p>For each problem, we established clear countermeasures and owners.</p><p>Looking retrospectively at our goals, we managed to have…🥁🥁🥁</p><blockquote>🙌 <strong>Zero delays for ongoing projects.</strong> 💪</blockquote><p>And we were… 🥁🥁🥁</p><blockquote>🙌 <strong>Ready in just one week. 💪</strong></blockquote><p><em>But we had to wait to ship our changes 😿. This happened because other projects took priority and we could not impact their work. Otherwise, the first objective would have suffered.</em></p><p>Despite this fact, the project was successful overall. We managed to overcome numerous unexpected issues without disrupting the ongoing work.</p><p>From three weeks of migration hell to one week of smooth sailing. The coffee tasted better that day.</p><h3>Embracing the AI world</h3><p>We already had a strong process, and we wanted to make it even stronger. The potential was huge.</p><p>The first step we took was to find ways to open up our scripts and tools to AI IDEs such as Cursor or ClaudeCode.</p><p>Since we use Swift scripting and those scripts are part of SPMs, we felt confident that we could decouple the core logic into separate packages. And we did just that.</p><p>This was key to start building our first MCPs (Model Context Protocol tools) in Swift. We then integrated the built Swift MCP into Cursor, and from there, we would feed the information to an Agent with precise Xcode migration details, such as the current Xcode versions, latest releases, and so on.</p><p>Fabulous!</p><p>At Qonto, we use <a href="https://dust.tt/">Dust</a> a lot. We have numerous agents delegated to resolve time-consuming tasks. You can read more about them <a href="https://medium.com/qonto-way/how-we-transformed-talent-acquisition-at-qonto-thanks-to-ai-3a17091955d6">here</a>.</p><p>What can go well with a frustrated person encountering issues from a migration that just happened? A Dust agent.</p><p>The idea was to create an agent that can troubleshoot, diagnose, and assist people with Xcode migration issues. And we did that.</p><p>Please meet Xcode Migrator 🤝:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKWi2LKxDJekMBd17Ih8ig.png" /><figcaption><em>Generated using </em><a href="https://www.midjourney.com/home"><em>Midjourney</em></a></figcaption></figure><p>The fun part is that it can be summoned on Slack through a simple emoji and can interact and respond directly in the Slack thread. It has context over the questions. People don’t have to go into their browser, log in to the Dust web app, search for this agent, and then type their problem there:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*qrqj_6aH2kqzf3YiCVHYAA.png" /><figcaption><em>Summoning Xcode Migrator</em></figcaption></figure><h3>Results</h3><p>The transformation speaks for itself:</p><ul><li><strong>From 21+ days to 5 days</strong> migration time (75% reduction)</li><li><strong>Zero disruption</strong> to ongoing team work across 60+ engineers</li><li><strong>90% team clarity</strong> (up from 33%) on migration processes</li><li><strong>Weekly automated notifications</strong> via Slack integration</li><li><strong>24/7 AI assistance</strong> reducing support tickets by eliminating manual troubleshooting</li></ul><p>Right now, we can perform an Xcode update in a few hours. For a codebase this large with 60+ engineers, it’s impressive. Why stop here? Let’s aim for 30 minutes, maybe less.</p><h3>The journey continues</h3><p>We started angry — frustrated with every new Xcode release. Even indie developers with large apps struggle with migrations. Some companies fall behind by over a year.</p><p>Imagine our situation back in the day:</p><ul><li>No Tuist to solve daily merge conflicts</li><li>Codebase shared with 60+ iOS Engineers</li><li>Tens of thousands of tests</li><li>Working with CocoaPods and SPM simultaneously</li></ul><p>Then we shaped the world we wanted to live in. We understood problems through data, previous migrations, and systematic improvement.</p><p>With small steps, we created tools, automated processes, and delivered solutions that actually worked. Xcode Release Checker was born. We had fun.</p><p>The team gave feedback about communication effectiveness. We listened, acted, made our process visible, created troubleshooting guides, and built a migration portal. We improved communication and solved problems. For real.</p><p>We created a CLI automating manual migration steps. Our Xcode 16 test threw weird errors at us — but we were prepared through early beta testing.</p><p>Most importantly: we kept Xcode migrations as background tasks without affecting people’s work. No more three-week migration nightmares.</p><p>AI transformed our productivity. We created MCPs in Swift, exposing tools to LLM clients. We built Xcode Migrator, a Dust agent ready to help with migration headaches.</p><p>The future looks bright. Or more liquid. Or more liquid glass.</p><p>Future Xcode version, here we come!</p><p><em>Thank you for taking the time to read our story. May the Force be with you! 🙏</em></p><h4>About Qonto</h4><p>Qonto is Europe’s leading finance management solution serving over 600,000 SMEs and freelancers across 8 countries. Launched in 2017 by Alexandre Prot and Steve Anavi, Qonto combines business finance with powerful financial tools including invoicing, bookkeeping, and spend management — all in one seamless solution. Backed by €600+ million in funding and powered by a team of 1,600+ people, Qonto is transforming how European businesses manage their finances with innovative products, transparent pricing, and 24/7 customer support.</p><p>Interested in joining a challenging and game-changing company? Take a look at our <a href="https://qonto.com/en/careers">open positions</a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2590657e809" width="1" height="1" alt=""><hr><p><a href="https://medium.com/qonto-way/xcode-migrations-from-stone-age-to-ai-mastery-d2590657e809">Xcode Migrations: From Stone Age to AI Mastery</a> was originally published in <a href="https://medium.com/qonto-way">The Qonto Way</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>