Reconstruction: How to Do Refactoring Usefully
summary
Refactoring is described as work that adds no new features but consumes developers’ time; the talk analyzes why refactoring tasks arise, how to handle them effectively, and whether it’s possible to prevent them in a product. It discusses practical approaches to manage and minimize refactoring overhead, with attention to architecture and cross-cutting concerns.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:03What is refactoring
- 5:42Benefits of refactoring
- 8:33Refactoring history
- 9:56When refactoring needed
- 11:25Legacy code problems
- 15:42Risks of bad code
- 17:12Proving refactoring necessity
- 19:42Starting refactoring
- 22:13Refactoring responsibility
- 25:20Refactoring plan and estimate
- 27:07Agreeing with manager
- 29:55Pre-refactoring prep
- 31:42Refactoring challenges
- 32:23Why refactoring fails
- 34:10When refactoring done
- 35:55Metrics and results
- 36:58Summary and advantages
- 38:25Refactoring and burnout
- 39:06Quick tips
- 40:58Q&A
related talks
50mRefactoring Is Not Just Clickbait
37mDon't Change the Project, Change Your Project
01h 12mLegacy Refactoring
36mRewrite, Rework or Refactor
52mHow to work with legacy so neither you nor the project burns out
51mIn the World of Refactoring
01h 17mRefactoring the ROI of Software
02mWe interview Vicente Baixauli and Paco Navarro