A How-to guide for migrating legacy data applications
summary
A team takes ownership of a decade-old mission‑critical data pipeline and modernizes it by automating large-scale edits across tens of thousands of files, running continuous smoke tests against production workloads to validate changes, and building an AST-based structural refactoring tool on top of ripgrep, pip‑modernize and pyupgrade. The plan includes a six‑month window of low feature work to pay down technical debt, clearer docs and onboarding, targeted instrumentation, and prioritized payoff features so the migration actually reduces maintenance cost and risk.
AI-written summary · about
chapters (7)
- 0:00Legacy migration challenges
- 6:28Evaluating whether to modernize the system
- 10:41Goals for modernization
- 16:46Automate testing & refactor
- 23:51Balancing needs during migration
- 28:39Post-migration maintenance
- 29:00Q&A on pipelines
related talks
23mDevOps and Legacy Code
55mSo, you inherited a large code base...
01h 06mRewriting Legacy Code
35mUpgrading Legacy Projects: Lessons Learned
25mMass migrations to the cloud
28mLarge scale refactoring: from start to finish
20mModernizing the Data Science Toolkit of a 40-year-old Market Research Company
50mMigrating Your Most Critical Feature Without Regressions or Downtime