Putting “Better” Before “Faster”

Contents
Even at 80, my mother remains actively involved in various community and social activities. A few days ago, I learned that she was preparing to give a talk based on a newly released government report running over 10,000 Chinese characters. I couldn’t help but worry about her. After all, reading and distilling such a lengthy, rather dry document is no small task. But as we talked, I discovered that she had already been using AI to organize the material, identify key points, and even compare previous versions to trace how the report had evolved. I was genuinely surprised. I knew she had started using AI to some extent, but I hadn’t expected her to incorporate it so naturally into her everyday work.
Almost without us noticing, AI has become part of more and more people’s daily lives. As a tool, it not only improves efficiency but also frees us from much of the tedious work that consumes our time, giving us more room to think, create, and ultimately produce better results. Yet this potential to make the outcome better seems to receive far less attention than it deserves. For now, much of the public conversation remains focused on how much more efficiently AI allows us to work.
Over the past few months, I’ve been working on a small project. When I first started, I gave serious thought to a question: Should I use AI to finish development faster, or should I use it to achieve a level of polish and maturity that would have been beyond my reach as a solo developer before AI? In the end, I chose the latter.
Given the project’s scope, I probably could have built a basic version in two or three weeks if I’d written all the code myself two years ago. Yet here I am, two or three months later, barely past the halfway point. And I have no regrets. I can genuinely feel that AI is helping me build something more solid, with results that are much closer to what I originally envisioned. Although I no longer write every line of code myself, I still maintain control over the details by moving forward in small steps and continuously verifying the results.
On the surface, development has slowed down. But looked at another way, much of the research, design, and refinement I’m doing now would previously have been abandoned or rushed through simply because I lacked the time and energy. Today, AI makes it possible for me to take on that additional work. It hasn’t made me less productive. Instead, it has allowed me to turn greater productivity into a higher level of quality and polish.
Of course, not everyone or every team will choose to invest the productivity gains from AI into improving quality. In a commercial environment especially, greater productivity often translates into tighter delivery deadlines. Last week’s widespread disruption to Microsoft’s email services, along with the nationwide ground stop imposed by the U.S. Federal Aviation Administration (FAA) following a failure in its air traffic control communications system, served as reminders of just how important the reliability of large-scale technical systems is. There is no evidence that either incident was caused by AI-generated code. Nevertheless, as AI continues to accelerate software development and delivery, whether testing, verification, and quality assurance can keep pace is a question the entire industry needs to take seriously.
I believe AI’s value should not be measured solely by how much time it saves or how much it reduces costs, but also by what it enables us to create. When efficiency becomes the easiest metric to measure, perhaps we should remind ourselves from time to time that the time and energy AI frees up can be used not only to do more and move faster, but also to do things better.
My hope is that everyone using AI, whether individuals or organizations, will continue to put “better” before “faster,” even as they pursue greater efficiency.
Recent Recommendations
How we rebuilt the Shopify app in 12 weeks
Not long after Shopify announced its return to native development in September, the company delivered an impressive result. In this article, Remi Vanhee explains how Shopify used coding agents to rebuild its mobile app from React Native into native Swift and Kotlin applications in just 12 weeks. Following the rewrite, Android startup time decreased by approximately 50%, app size shrank by 40%, and peak memory usage on iOS dropped by 70%.
As code generation becomes dramatically faster, development bottlenecks are shifting toward build resources, code review, merging, and team coordination. To give agents faster and more reliable feedback, Shopify introduced the Reflex architecture, which allows business logic to run independently of devices. Through a CLI, developers can load ViewModels, trigger Actions, and verify state in milliseconds. An internal tool called Helix uses the original app as a reference, breaking migration tasks into small, verifiable steps. Meanwhile, the team adjusted its development workflow through remote development environments, agent-assisted preliminary reviews, and pair programming, gradually shifting engineers’ focus from writing implementations to architecture design, verification mechanisms, and final decision-making.
The rewrite has sparked considerable discussion in the community. Did the 12 weeks include the initial architecture and tooling work? Could similar performance improvements have been achieved by investing equivalent resources in optimizing the original React Native app? And what will the long-term maintenance costs look like for two native codebases largely generated by agents? These questions will take time to answer. But Shopify’s experience demonstrates at least one thing: when code generation is no longer the primary bottleneck, architectural constraints, observability, and verification become even more important.
Breakpoints Go Grey When You Turn On the Xcode Compile Cache
After enabling Tuist’s compile cache in Xcode 27.1, Lee YoungJun found that his app built and ran normally, but breakpoints remained greyed out and never triggered. After investigating, he discovered that the problem wasn’t the cache itself, but a missing LLDB source file mapping for the virtual paths used in debugging information.
To make the compile cache independent of a project’s absolute path, Xcode 27 replaces source file paths in debugging information with virtual prefixes such as /^src. Although Tuist generates an LLDB initialization file containing cache-related configuration, the version the author was using lacked the target.source-map setting needed to map /^src back to the actual project directory. Ultimately, adding a single LLDB command restored the breakpoints.
What’s new in Swift: November 2026 Edition
Swift has published its November roundup of project and community updates, written by Dave Verwer and Dave Lester. The article opens with a reminder of an important approaching deadline: after a two-year transition period, CocoaPods will officially stop accepting new pods and version updates on December 2, 2026, entering read-only mode. While this won’t immediately break existing projects, teams that haven’t migrated yet should seriously consider moving to SwiftPM. As for SwiftPM’s own evolution, I’m particularly interested in SE-0545 (build performance debugging) and SE-0547 (SwiftPM compile caching), both of which have been accepted. Meanwhile, SE-0560 proposes introducing conditional dependencies based on build configurations such as Debug and Release.
As an independent developer, I rarely worried about compilation or testing times back when I wrote all my code by hand. But with agents working in parallel and test coverage expanding, the development process is undergoing a structural shift. Build efficiency, observability, and verification capabilities are becoming increasingly important. As CocoaPods approaches its official farewell, these recent SwiftPM improvements seem particularly well-timed, addressing emerging needs in modern development workflows at the toolchain level.
What is GlassEffectContainer in SwiftUI and how to use it
GlassEffectContainer is an important SwiftUI component for creating the merging and morphing animations of Liquid Glass elements. It not only allows adjacent glass shapes to merge naturally, but also works with glassEffectUnion, glassEffectID, and glassEffectTransition to control shape grouping and animations when elements appear or disappear. While explaining how to use these APIs, Sarun Wongpatcharapakorn also shares some interesting details discovered through hands-on testing.
The spacing parameter doesn’t simply determine the distance between shapes; it affects how far apart they can be before merging. Sarun found that two shapes separated by 12pt required the container’s spacing to be set to approximately 24pt before they began to touch. Another finding concerns glassEffectID: although Apple’s official examples use it to implement morphing animations, the author observed that animations still worked correctly without an ID in some scenarios. Conversely, in certain morphing transitions between different positions, specifying an ID actually caused the animation to jump abruptly.
Presenting contextual controls with SwiftUI’s inspector
SwiftUI’s inspector provides an adaptive contextual panel: it appears as a sidebar alongside the main content in wide layouts and automatically transforms into a sheet in compact environments. Compared with .sheet, it has received relatively little attention, especially on the iPhone. However, through testing on iOS 27.2, Natascha Fadeeva discovered that its behavior isn’t entirely consistent with that of a regular sheet. For example, after dismissing an Inspector with a downward swipe, it may fail to reopen; the width specified through inspectorColumnWidth may have no effect; and changing the selected detent through a Binding doesn’t dynamically adjust its height as it does with a regular .sheet.
Despite these remaining issues, the adaptive nature of inspector gives it more room to shine on devices such as the iPhone Duo, where available space changes as the device folds and unfolds.
Trust and Authorship
As AI becomes increasingly involved in creative work, an unprecedented tension is emerging between the quality of a work and the process through which its creator produced it. Drawing on the case of a novelist who lost a publishing opportunity over suspected AI use, as well as the controversy surrounding AI disclosure in the indie game Big Walk, Matthew Massicotte explores the increasingly complicated relationship between authorship and public trust in the AI era.
In Matthew’s view, the issue isn’t simply how much AI was used, but that creators and audiences may have fundamentally different understandings of what authorship means. Failing to disclose AI use could eventually be seen as concealment, while voluntarily disclosing it may trigger immediate backlash. Even creators who haven’t used AI at all can suffer from false accusations. When people can no longer judge how much personal effort a creator invested simply by looking at the finished work, trust becomes increasingly fragile.
A few days ago, a song with human-written lyrics and AI-assisted composition and vocals topped Melon TOP100, one of South Korea’s most influential music charts, sparking concern and discussion across the music industry and wider society. Perhaps a considerable portion of listeners don’t care much about how a work was created. From another perspective, however, AI may also act as a catalyst for public sentiment, further amplifying discussion and exposure around a work.
As Matthew discusses, attitudes toward AI-assisted creation vary significantly across different fields and cultural contexts. In my view, the quality of the work itself remains essential, but the creative process can also influence how people perceive its value. Using AI doesn’t necessarily diminish a work’s value, just as the absence of AI should never automatically be taken as a guarantee of quality.
Tools
Yardlet: A Native Multi-Agent Workspace Built with Swift
Yardlet is an open-source macOS coding agent workspace built with Swift and SwiftUI by Jeongki Park. It supports managing multiple agents, including Claude Code, Codex, OpenCode, and Antigravity, within a single window. It uses existing CLI accounts and sessions, obtaining runtime status through native protocols without installing global hooks or modifying agents’ global configurations. It also provides multi-account management, token usage statistics, diff review, MCP connectors, browser automation, and remote control from mobile devices or other Macs.
The author has also written a technical comparison of nine desktop coding agent tools, examining how they obtain agent status, modify the runtime environment, and differ in memory overhead. Rather than simply comparing features, the article offers a more interesting look at how different integration approaches affect the development environment.
Heimdall: Managing App Store Connect Safely with AI Agents
Heimdall, developed by Eray Endes, is an open-source MCP server that exposes the App Store Connect API and App Store Server API as tools callable by AI agents. It covers app releases, TestFlight, subscription management, customer reviews, sales data, and more. The project organizes its tools into profiles based on business scenarios and provides higher-level operations such as cross-region subscription pricing, review summaries, and draft replies.
Compared with tools that focus primarily on API coverage and automation capabilities, Heimdall places greater emphasis on operational safety. It stores API credentials in the macOS Keychain, supports read-only mode, and requires explicit human confirmation for high-risk operations such as price adjustments and permission changes. These design choices also extend its potential audience beyond developers to non-technical roles such as operations, marketing, and customer support.