How to Lift Your Tech Debt Curse with the Magic of the Open-Close Principle

on YouTube ↗19m

" summary

Claim: apply the Open-Closed Principle to refactor fragile Python production code without changing behavior, using small, tested steps. The code example transforms a single get_payment function into a DateRange dataclass, an Order parameter object, extracted helper methods, a notification decorator, and a location-specific subclass for discount logic. Refactoring shrinks the long method, shortens the parameter list, removes magic numbers, and preserves results after each change. Recommended tooling: dataclass and parameter object, extracted methods and tests.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and story
2. 2:14Tech debt curse explained
3. 3:18Code smell examples
4. 7:35Refactoring for clarity
5. 13:15Refactoring principles
6. 15:45Open-Close Principle
7. 17:33Conclusion and simplicity

" related talks

• 44mRefactoring from Good to GreatBen Orenstein · Aloha RubyConf 2012
• 47mRefactoring from Good to GreatBen Orenstein · RubyConf 2012
• 31mTechnical Lessons Learned from Pythonic RefactoringYenny Cheung · PyCon.DE 2017
• 33mElegant Solutions For Everyday Python ProblemsNina Zakharenko · PyCon 2018
• 57mTechnology mix: From legacy to clean architectureGrzegorz Kocjan · 4Developers 2020
• 48mRefactoring from Good to Great - A Live-Coding OdysseyBen Orenstein · RubyConf AU 2013
• 47mHow to Fix Your Technical Debt DilemmaJonathan Schneider · Devnexus 2023
• 24mOpen Close Principle, is it what you thought?Thomas Dutrion · phpDay 2019