Out of the Legacy Trap: From Technical Debt to Higher Quality
summary
Discusses how to incrementally improve software quality in legacy Java systems and ensure quality in new projects by applying practices like Clean Code, software architecture principles, and CI/CD. Also addresses the role of management in enabling and sustaining these quality improvements.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:34Agenda
- 5:09Characteristics of Technical Debt
- 8:27Incurring Technical Debt
- 11:56Causes of Technical Debt II
- 15:43Impact of Technical Debt
- 17:52Timeline of Technical Debt
- 18:44Testing Technical Debt
- 20:08Ensuring Software Quality
- 22:42Software Quality - Code Level
- 27:51Software Quality - Architecture
- 33:41Process Improvements
- 34:43Agile Practices: New Definition of Done & Ready
- 35:38Management
related talks
51mThe Void of Legacy: A Strategy for Radical Improvements in a Project
53mLegacy: how to win the race. Viktor Polishchuk. Java Fest 2020 Online
53mCongratulations! Legacy code guru level unlocked!
54mThe Future of the Past – Legacy Will Stay With Us
50mWe ♥️ legacy
52mHow to work with legacy so neither you nor the project burns out
45mTechnical Debt: Taking back control when it's already messed up
52mOMG, What a Beautiful Legacy