Living with your Legacy
summary
Lots of legacy systems still run critical business workloads: examples include VB6 and FoxPro 2.6 and enterprises with COBOL on DB2 (industry estimate ~200 billion lines of COBOL still in use). Practical tactics: keep old dev environments in virtual machines, put code in Git, add tests and refactor only the code you touch, and use an HTTP endpoint as an anti‑corruption layer plus an ORM exposing DB2 views to build a modern front end with CQRS. Research shows reducing technical debt increases developer productivity so focused maintainability pays off.
AI-written summary · about
chapters (9)
- 0:00Start
- 7:50WHAT IS LEGACY?
- 9:03DESIGN 15 YEARS OLD. LEGACY EFFECTIVELY LEGACY CODE
- 24:37HERO PROBLEM
- 30:52ASSESS TECHNICAL DEBT Also: tech debt was hindering maintenance, implementation of new features
- 35:17REDUCE BUGS
- 47:38WHAT ABOUT ADDING TESTS? TESTS HELP AVOID SIDE EFFECTS OF REFACTORING CODE
- 54:15WINFORMS & WPF LIFE EXTENSION WITH .NET CORE 3.0
- 55:50WORKING ON LEGACY CODE DOES NOT HAVE TO SUCK IS NOT A CAREER KILLER IS WHAT MOST OF US DO IN REAL LIFE
related talks
26mLegacy Codebases are a DevOps Issue
14mDo Legacy Systems dream of Modernization?
47mLegacy Software: Really a Problem?
55mModernizing Legacy Code - While Not Bringing Down Prod
54mThe Future of the Past – Legacy Will Stay With Us
49mWhat Does a Legacy System Teach Us?
21mTransforming Legacy Systems: A DevOps Journey to Modernization
52mOMG, What a Beautiful Legacy
