Legacy Evolution – The Innovation Opportunity!
summary
Argues for a data‑centric, lean replacement path that avoids big rewrites by landing narrow, high‑value changes in 3–4 month timeboxes and proving them at scale; examples include converting dozens of Excel rule sheets into a rule interpreter that replaces ~100 developers with two maintainers, adding a TCP/IP board and exposing process control as Atom feeds, fronting legacy MRP with ODBC fronted MRP for instant reporting, and doing a physical DB page migration validated by an independently written checker using property‑based testing — all deployed and working.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:41Legacy?
- 5:31Legacy Evolution Value Proposition
- 6:17Typical Code Centric Approaches
- 8:10Avoid Big Bang Systemic Changes
- 10:58Leverage Innovations
- 19:39Selective Code Focus
- 22:00Lean Data and Flow Centric Approach Why focus on Data and Flows?
- 25:04Legacy Innovation Patterns
related talks
43mHow to Innovate in a Legacy
47mLegacy Software: Really a Problem?
48mLegacy, for lack of a better word, is good
20mLegacy Migration... Differently
01h 27mRedesigning Legacy Systems : Keys to Success
43mPatterns of Legacy Displacement
44mLegacy Software Really a Problem
41mLegacy, for lack of a better word, is good