Refactoring the ROI of Software
summary
Argues that automated, repeatable refactors using OpenRewrite turn maintenance into measurable ROI by creating PRs that are validated in a separate pipeline and merged when ready. Proposes a dual-pipeline model — CI/CD for features and continuous migration (CICM) for upgrades — that detects drift, runs recipes, and shrinks remediation windows. Gives concrete wins: a customer saves $50,000/month on a VM change and a demo shows a Java 8 → Java 24 upgrade cutting a 490MB footprint to ~22.6MB and enabling further platform optimizations.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 7:06Why migrations are hard
- 12:40Introducing CICM
- 25:06Demo of OpenRewrite
- 36:19Typical journey to adoption
- 48:47Continuous migration as strategy
- 1:02:22Q&A
related talks
52mRefactoring the ROI of Software Continuous Mondernization with Tanzu Platform
41mOpen Rewrite – Dive in Automated Refactoring
47mHow to Fix Your Technical Debt Dilemma
46mRewrite Vs Refactor
40mHow to sell a big refactor or rewrite to the business?
01h 12mLegacy Refactoring
36mRewrite, Rework or Refactor
50mRefactoring Is Not Just Clickbait