Seams: How to Test Legacy Code Without Breaking Production (Michael Feathers)

Video Description

Learn Michael Feathers' seam concept—the surgical technique for making legacy code testable without risky rewrites. This video breaks down the core idea from Working Effectively with Legacy Code: how to alter behavior without editing code, identify the three types of seams, and break hard-coded dependencies incrementally. Perfect for developers dealing with untestable legacy codebases who need a safe, incremental path to adding tests and refactoring confidently. 📚 What you'll learn: • What a seam is and why it solves the testing catch-22 • The crucial difference between seams and enabling points • Three types of seams: object, link, and preprocessing • How to use Extract Interface to create object seams • Real-world scenarios: singletons, databases, time-dependent code, APIs • When seams are appropriate vs. when to refactor directly • Common misconceptions about seams and dependency injection • How seams connect to Strategy Pattern, Adapters, and Strangler Fig • A step-by-step action plan for surgical legacy code modernization 🎯 Your action plan: Start with one untestable class. Extract an interface for the hard-coded dependency. Inject it through the constructor. Write tests with mocks. Use that safety net to refactor toward cleaner architecture. One seam at a time. 💡 If you're working with legacy code and need practical techniques that work in production, subscribe for more testing strategies and modernization patterns. Timestamps: 0:05 Michael Feathers' Seam Concept 0:38 The Testing Problem 1:15 What is a Seam? 1:50 Three Types of Seams 2:22 Object Seam: Before 2:58 Object Seam: After 3:34 Link Seam Example 4:20 Creating Seams: Extract Interface 5:01 Real-World Seam Scenarios 5:44 When to Use Seams 6:21 Common Misconceptions 7:04 Seams and Other Patterns 7:40 Your Action Plan