How to spend four years and a bag of money refactoring and launch nothing
summary
Describes Ultimate Guitar’s experience deciding to replace a large legacy backend: explains why rewriting everything is dangerous, what problems prompted the plan, and the consequences of spending four years and large funds on refactoring without delivering a working replacement. Discusses practical pitfalls of full rewrites in large, long-lived projects rather than incremental approaches.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:23Old code problems
- 13:49Refactoring mistakes
- 21:56Finding alternatives
- 25:48Incremental migration
- 33:50Results and conclusions
- 35:44Q&A
related talks
40mHow to sell a big refactor or rewrite to the business?
36mRewrite, Rework or Refactor
23mRefactoring Go in Large Codebases
42mSo You Want To Rewrite That...
48mLegacy, for lack of a better word, is good
52mHow to work with legacy so neither you nor the project burns out
37mDon't Change the Project, Change Your Project
51mTo Re-write Or Not To Re-write