Get better at Refactoring
summary
Claim: refactoring measurably reduces the cost of change and cycle time (aiming toward weekly releases). Demonstration works on a Java Spring MVC mail controller with tests, using IntelliJ refactorings and unit tests to keep behavior stable. Steps shown: replace temporary variables, move address parsing into the form/contact model, inline duplicates, extract responsibilities from the controller, and run tests after each step. A real legacy case took three days to remove duplication; the demo refactorings keep tests passing while improving cohesion.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:15Agenda
- 5:25Story
- 5:47Changing a footer
- 10:08Causal loop diagram
- 13:47Legacy code
- 20:18Refactoring
- 24:35Code Overview
- 25:13Development
- 25:44Code walkthrough
- 34:13Replace subject
- 35:57Duplication
- 37:09Duplicates
- 39:14Single Responsibility Principle
- 41:44Testing
- 44:01How to do better
- 46:03Similar responsibilities
- 46:46Recap
- 48:46Teaching Refactoring
