Don’t Write Legacy Swift

This article explores the concept of 'legacy Swift' through the lens of Michael Feathers' definition that legacy code is code without tests. The author, a developer transitioning from Objective-C to Swift, argues that even new Swift code can become legacy if untested. They share personal struggles with test-driven development (TDD), emphasizing the difficulty but ultimate value of writing unit tests. The piece advocates for integrating testing into the development process to ensure code quality, maintainability, and confidence in software behavior. It targets iOS/macOS developers and aligns with IT/TECHNOLOGY topics like software engineering, best practices, and testing methodologies.