Andrew Bancroft • 12/10/2014

Don’t Write Legacy Swift

This article discusses the concept of 'legacy Swift' inspired by 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) and unit testing, acknowledging the difficulty but advocating for the long-term benefits. The piece encourages developers to prioritize writing tests alongside production code to ensure code quality and maintainability, warning against postponing tests.

0 comments

#unit testing #test-driven development #legacy code