Bringing Clean Code to large scale legacy Applications
summary
Practical plan: focus refactoring on hotspots not the whole million‑to‑ten‑million‑line mess, add tests (start with integration then carve unit tests), use profilers and static analyzers, and prefer straightforward modern C++ (or Boost substitutes) so optimizers help instead of hindering. Expect short wins like cutting 40‑minute full builds and reducing repeated two‑to‑three‑day fixes to hours, avoid big rewrites, and use IDE refactor tools and compile‑time tricks. target pain points first measure before and after keep changes small and reversible
AI-written summary · about
chapters (35)
- 0:00Introduction
- 0:36Title
- 2:31Legacy Code
- 4:44Largescale
- 5:27No map
- 6:29Clean Code C
- 7:37Clean Code Book
- 8:41Principles
- 10:57Performance
- 15:03We have to apply new features
- 15:32Team culture
- 16:41Make people aware of problems
- 18:00Habits
- 20:30Awareness
- 21:19Resistance
- 23:10Silos
- 24:29Bad apples
- 25:48Legacy processes
- 26:50Refactoring
- 27:51Testdriven development
- 28:39Refactoration
- 31:25Pain Points
- 32:45Goals
- 36:24Daily Maintenance
- 38:42Decoupling
- 41:12Old Architecture
- 42:05Rewriting
- 42:50Cons
- 46:10Tools
- 47:36Switching Compilers
- 49:00Property Extensions
- 49:42Overload Functions
- 50:59Factoring Out Functions
- 52:58Costs
- 53:41Questions
