Five Lines of Codes
summary
Starts from a chaotic codebase with red tests and a bus factor of one and applies an iterative, compiler-driven refactoring workflow: remove dead weight, enforce Improvement Monday mob sessions with Strong-style pairing, introduce tiny, syntactic rules like Five lines and safe copy‑paste steps, and use the type system and static analysis instead of brittle tests. The process produces localized invariants, eliminates enums and switches into classes, reduces coupling, and turns a notorious repo into a productive, happy team that actually ships.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:25A new project
- 3:31Dead weight
- 4:56Strong-style pairing
- 5:26Safety
- 6:52The code
- 7:44The environment
- 12:57The smells
- 16:07From smells to rules
- 16:37Five lines: Statement
- 24:59Type code elimination: Flow
- 32:02Trail map: Summary
- 34:51Outro
related talks
32mFive Lines of Code
35mQuickly and Safely Refactoring Legacy Code
53mIntentional Code - Minimalism in a World of Dogmatic Design
48mThree Principles To Bring Your Legacy Code Into the Future
18mWriting Quality Code
48mRefactoring from Good to Great - A Live-Coding Odyssey
33mBuilding Code Quality
29m6 Safe Refactoring's for Untested Legacy Code